Database Develop

[Q] Is there ANY WAY to fix this? ):

Please help me through this, as I am not familiar with the terms used to describe certain things I'm the process that I've seen in my research.
My buddy gave me this AT&T Galaxy Note 3 and told me it was ****ed up... It had been rooted and It was stuck in a boot loop at first and I tried to fix it with Odin or some **** and now anytime I try and turn it on it says "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again" but kies wouldn't read the phone. It's annoying but I wanna fix it. When it says it needs firmware blah blah ... It also says this in the top left:
ODIN MODE
PRODUCT NAME: SM-9000A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, A2, A3, P2
WRITE PROTECTION: Enable
UDC START
please for gods sake help me

It appears to be download mode. Try taking battery out for a minute then try to power up. If that doesnt work hold power dwn+home button+volume up at the same time to try and get to stock recovery. If it does boot to stock recover just click reboot device
FireKatV11...FireGearV16

whiteguccimane said:
Please help me through this, as I am not familiar with the terms used to describe certain things I'm the process that I've seen in my research.
My buddy gave me this AT&T Galaxy Note 3 and told me it was ****ed up... It had been rooted and It was stuck in a boot loop at first and I tried to fix it with Odin or some **** and now anytime I try and turn it on it says "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again" but kies wouldn't read the phone. It's annoying but I wanna fix it. When it says it needs firmware blah blah ... It also says this in the top left:
ODIN MODE
PRODUCT NAME: SM-9000A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, A2, A3, P2
WRITE PROTECTION: Enable
UDC START
please for gods sake help me
Click to expand...
Click to collapse
You have a good guide HERE explaining the process step by step. Good luck

You can still save it. You just need to get latest samsung mobile drivers downloaded on your pc
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

Bricked? SM-T377A Galaxy Tab E. Help

I was attempting to remove the FRP on this ATT version when I did something terribly wrong. It now will only allow me to enter download mode. I tried to flash all versions I could find for the stock firmware and ODIN fails at boot.img. I tried with PIT and without and all sorts of variations. No luck.
Download mode shows:
ODIN MODE
PRODUCT NAME SM-T377A
CURRENT BINARY SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
FRP LOCK ON
SECURE DOWNLOAD ENABLED
KNOX WARRANTY VOID 0 0X0000
AP SWREV B3 K1 S2
Regular booting says:
An error has occurred while updating the device software. Use the emergency recovery function in smart switch PC software
What exactly do i need to flash to unbrick this? I have spent at least 20 hours on this.

It4sd said:
I was attempting to remove the FRP on this ATT version when I did something terribly wrong. It now will only allow me to enter download mode. I tried to flash all versions I could find for the stock firmware and ODIN fails at boot.img. I tried with PIT and without and all sorts of variations. No luck.
Download mode shows:
ODIN MODE
PRODUCT NAME SM-T377A
CURRENT BINARY SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
FRP LOCK ON
SECURE DOWNLOAD ENABLED
KNOX WARRANTY VOID 0 0X0000
AP SWREV B3 K1 S2
Regular booting says:
An error has occurred while updating the device software. Use the emergency recovery function in smart switch PC software
What exactly do i need to flash to unbrick this? I have spent at least 20 hours on this.
Click to expand...
Click to collapse
Sounds like you need too flash new firmware first . This happened to me the first time I rooted and added a custom ROM on a galaxy note 8. I would also be sure you have adb set up on the pc. I am pretty new at this. Still learning, these are a couple things I had to do my first time.

Johnydmic said:
Sounds like you need too flash new firmware first . This happened to me the first time I rooted and added a custom ROM on a galaxy note 8. I would also be sure you have adb set up on the pc. I am pretty new at this. Still learning, these are a couple things I had to do my first time.
Click to expand...
Click to collapse
Although the Tab E has a different OS Samsungs firmware seems to all work the same for the most part.

Issues flashing SM-G920A

Hello all
I tried flashing the device using Odin and everything downloads successfully. The phone will reboot and during the system update process, it fails at 32% each time. The phone then freezes on "Erasing". I can redo the Odin process and each time it just fails at 32% during the update process. I am unable to boot the phone into recovery mode. Smart Switch also does not recognize the device that was why I attempted the Odin process in the first place. The only thing I am able to do to this point is put the phone into Odin mode. I have been flashing G920AUCS7ERC1_ATT7ERC1 using Odin 3.13.1 Patched.
In Odin mode the device shows
PRODUCT NAME: SM-G920A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0X0000)
RP SWREV: B:5 K:3 S:3
A little backstory... This phone belongs to my mother. She thinks she downloaded some applications and this sent the phone into a bootloop. A soft reset leads to a screen showing "No command". I am unable to do anything further with the device. I am really just looking to get the phone to boot so I can image the device and pull whatever data from it that I can.
Thank you for any help you can provide.

Probably phone can't access DRK.
System Status: Custom on a locked bootloader means someone tried to repair the DRK using a combination firmware, but didn't finish the job. You will need a factory binary on Nougat, which will boot the phone, then will need to repair the DRK. Or if you don't, flash an efs backup through Odin in download mode.

I flashed in G920AUCU5DQB3_FIX_DRK_dm-verity that I located through these forums and now the phone will freeze on the "Samsung" screen just as the device is detected through USB but then the phone restarts and loops again. This is the furthest I have made it so far lol

Look up combo firmware G920AUCU6AQC1, that appears to be a 2017 release so it probably has the same bit increment as nougat

Teracotta said:
Look up combo firmware G920AUCU6AQC1, that appears to be a 2017 release so it probably has the same bit increment as nougat
Click to expand...
Click to collapse
When I attempt to flash this firmware, the process fails and "SW REV. CHECK FAIL. DEVICE: 5, BINARY: 4" is displayed on the phone. I tried using different cables and multiple attempts with the same results each time.

Kromah02 said:
When I attempt to flash this firmware, the process fails and "SW REV. CHECK FAIL. DEVICE: 5, BINARY: 4" is displayed on the phone. I tried using different cables and multiple attempts with the same results each time.
Click to expand...
Click to collapse
That is the knox bitlock which means that you are on a newer bootloader than the combo firmware. However, G920AUCU6AQC1 should be a newer firmware, and shouldn't interpret that as binary: 4. I am guessing it's a wrong display.
You may need a box to boot it out. See this topic which hits on your exact firmware:
http://forum.gsmhosting.com/vbb/f684/sm-g920aucs7-dm-verity-error-question-solved-2367622/
On dm-verity error I think fix efs function gets the phone to boot.

dave357 said:
Actually you can downgrade to 6.0.1 and any Revision aka BIT 5 firmware. The reason for this is that the Rev 7 or 7.0 Firmware has the same bootloader firmware as 6.0.1 as long as its BIT 5 aka Rev 5 Firmware you are flashin. Also use Odin 3.13.3 SHAE 256 Fix_ATT_Verizon. PrinceComsy Odin may work as well. But I have done several of these downgrades on G920A with no issues-
Click to expand...
Click to collapse
This is worth a shot, try to back to the most recent Marshmallow firmware, then flash the Marshmallow combo rom.

Note 9 bricked ? N960F DS

Hello samsung gurus! I think I've bricked my phone
A few days ago I tried flashing a custom rom (didn't even get to that part but that was my goal).
I was on DBT XXU2CSA2 with XXU2CRTL so I tried flashing other stock roms (only XXU2) via download mode with Odin 3.13.1 and it didn't work it said something like Custom binaries are not allowed to be flashed due to KG locked (BOOTLOADER).
Then I entered recovery and made a factory reset and selected reboot to bootloader and when I tried to flash a rom (stock XEU XXU2ARJ1) it worked ... now I went and enabled the developer mode ... checked OEM Unlock which restarted my phone ... enabled usb debugging because I was preparing for flashing twrp.
Put the phone in recovery and choose reboot to bootloader after that I flashed twrp and then it booted into it.
I was going to flash Dr.Ketan rom and after I downloaded the files I saw that there was a file BL_N960FXXU2CSA2_CP_N960FXXU2CRLT_extract_this_first.zip so I thought that I need to flash that first so I rebooted my phone from twrp pressed vol down + bixby which got me directly into download mode and flashed the bl and cp from odin and this is where all ended it didn't work as it said :
All binaries are not allowed to be flashed due to KG Locked. (RADIO)
And when I restarted my phone the only thing that appears on the screen is: Custom binary blocked due to remaining installment balance. Even when I plug the charger in I get this message and no charger animation So now I can't boot intro recovery because I flashed twrp .. and when I boot in download mode anything that I try to flash ends with the message:
All binaries are not allowed to be flashed due to KG Locked.
When I boot in download mode I get the following details:
PRODUCT NAME: SM-N960F
CURRENT BINARY: Custom
KG STATE: LOCKED
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = MAX77705 hw: 3 main: 30
WARRANTY VOID: 1 (0x030c)
AP SWREV: B:2 K:2 S:2
and a bunch of other info (DID, LOT_ID, CHIP_ID, nAsv_TABLE, nAsv_CPUCL0, nAsv_CPUCL1, nAsv_G3D, nAsv_MIF, nAsv_INT, nAsv_CAM_DISP, nAsv_CP, nAsv_PMIC, nAsv_PMIC_CP, nAsv_FSYS, product_line, asb_version, ids_big, ids_g3d, PMIC_ID, LPDDR4 manufacturer, LPDDR4 process ver, LPDDR3 size)
and anything I try to flash (i tried all files from DBT XXU2, also individual files like just BL/AP/CP/CSC and even individual imgs like sboot, boot, recovery, system, cache) and always the same message All binaries are not allowed to be flashed due to KG Locked.
Is my phone really bricked ? Anybody have any tips on what should I do ? I searched for 2 days for any solution and didn't find anything specific for N960F and solutions for other models didn't work, also nothing comes up on searches on KG STATE :crying:

Have you tried Smart Switch?

moromindful said:
Hello samsung gurus! I think I've bricked my phone
A few days ago I tried flashing a custom rom (didn't even get to that part but that was my goal).
I was on DBT XXU2CSA2 with XXU2CRTL so I tried flashing other stock roms (only XXU2) via download mode with Odin 3.13.1 and it didn't work it said something like Custom binaries are not allowed to be flashed due to KG locked (BOOTLOADER).
Then I entered recovery and made a factory reset and selected reboot to bootloader and when I tried to flash a rom (stock XEU XXU2ARJ1) it worked ... now I went and enabled the developer mode ... checked OEM Unlock which restarted my phone ... enabled usb debugging because I was preparing for flashing twrp.
Put the phone in recovery and choose reboot to bootloader after that I flashed twrp and then it booted into it.
I was going to flash Dr.Ketan rom and after I downloaded the files I saw that there was a file BL_N960FXXU2CSA2_CP_N960FXXU2CRLT_extract_this_first.zip so I thought that I need to flash that first so I rebooted my phone from twrp pressed vol down + bixby which got me directly into download mode and flashed the bl and cp from odin and this is where all ended it didn't work as it said :
All binaries are not allowed to be flashed due to KG Locked. (RADIO)
And when I restarted my phone the only thing that appears on the screen is: Custom binary blocked due to remaining installment balance. Even when I plug the charger in I get this message and no charger animation So now I can't boot intro recovery because I flashed twrp .. and when I boot in download mode anything that I try to flash ends with the message:
All binaries are not allowed to be flashed due to KG Locked.
When I boot in download mode I get the following details:
PRODUCT NAME: SM-N960F
CURRENT BINARY: Custom
KG STATE: LOCKED
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = MAX77705 hw: 3 main: 30
WARRANTY VOID: 1 (0x030c)
AP SWREV: B:2 K:2 S:2
and a bunch of other info (DID, LOT_ID, CHIP_ID, nAsv_TABLE, nAsv_CPUCL0, nAsv_CPUCL1, nAsv_G3D, nAsv_MIF, nAsv_INT, nAsv_CAM_DISP, nAsv_CP, nAsv_PMIC, nAsv_PMIC_CP, nAsv_FSYS, product_line, asb_version, ids_big, ids_g3d, PMIC_ID, LPDDR4 manufacturer, LPDDR4 process ver, LPDDR3 size)
and anything I try to flash (i tried all files from DBT XXU2, also individual files like just BL/AP/CP/CSC and even individual imgs like sboot, boot, recovery, system, cache) and always the same message All binaries are not allowed to be flashed due to KG Locked.
Is my phone really bricked ? Anybody have any tips on what should I do ? I searched for 2 days for any solution and didn't find anything specific for N960F and solutions for other models didn't work, also nothing comes up on searches on KG STATE :crying:
Click to expand...
Click to collapse
first time I've herd of KG state.
get samsung smart switch and go to the emergency recovery menu incase that works.

Rosli59564 said:
Have you tried Smart Switch?
Click to expand...
Click to collapse
i tried smart switch latest version and while in download mode it says unrecognized phone ... i also downloaded a version where the device initialization is available .... entered the s/n from the back of the phone and it says n960f doesn't support initialization ... so no luck with smart switch either

I'm on pie and I found in developers options the 6st option down in the row is to unlock bootloader. This is the first time that I've sean something like that and I don't know what's it for but maybe it's your case.
EDIT: sorry, I realized that you already used it.

moromindful said:
i tried smart switch latest version and while in download mode it says unrecognized phone ... i also downloaded a version where the device initialization is available .... entered the s/n from the back of the phone and it says n960f doesn't support initialization ... so no luck with smart switch either
Click to expand...
Click to collapse
check your xda pm for solution

gsmfixer said:
check your xda pm for solution
Click to expand...
Click to collapse
This is still not resolved.
I tryed flashing combination files still the same message in download mode: All binaries are not allowed to be flashed due to KG Locked.
When booting recovery: Custom binary blocked by remaining installment balance
When normal boot same message as in recovery
So if anyone have any ideea what should I try please chip in ...
I will gladly pay for any service related to unbricking my phone or at least guiding me to unbricking it if this is possible.

I added some photos. Still no solution yet

Did you try to flash lastest stock android pie rom

malucthuyquai said:
Did you try to flash lastest stock android pie rom
Click to expand...
Click to collapse
I tried to flash stock rom. full files, partial files ... all give me the same error All binaries are not allowed to be flashed due to KG locked.

moromindful said:
Hello samsung gurus! I think I've bricked my phone
A few days ago I tried flashing a custom rom (didn't even get to that part but that was my goal).
I was on DBT XXU2CSA2 with XXU2CRTL so I tried flashing other stock roms (only XXU2) via download mode with Odin 3.13.1 and it didn't work it said something like Custom binaries are not allowed to be flashed due to KG locked (BOOTLOADER).
Then I entered recovery and made a factory reset and selected reboot to bootloader and when I tried to flash a rom (stock XEU XXU2ARJ1) it worked ... now I went and enabled the developer mode ... checked OEM Unlock which restarted my phone ... enabled usb debugging because I was preparing for flashing twrp.
Put the phone in recovery and choose reboot to bootloader after that I flashed twrp and then it booted into it.
I was going to flash Dr.Ketan rom and after I downloaded the files I saw that there was a file BL_N960FXXU2CSA2_CP_N960FXXU2CRLT_extract_this_first.zip so I thought that I need to flash that first so I rebooted my phone from twrp pressed vol down + bixby which got me directly into download mode and flashed the bl and cp from odin and this is where all ended it didn't work as it said :
All binaries are not allowed to be flashed due to KG Locked. (RADIO)
And when I restarted my phone the only thing that appears on the screen is: Custom binary blocked due to remaining installment balance. Even when I plug the charger in I get this message and no charger animation So now I can't boot intro recovery because I flashed twrp .. and when I boot in download mode anything that I try to flash ends with the message:
All binaries are not allowed to be flashed due to KG Locked.
When I boot in download mode I get the following details:
PRODUCT NAME: SM-N960F
CURRENT BINARY: Custom
KG STATE: LOCKED
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = MAX77705 hw: 3 main: 30
WARRANTY VOID: 1 (0x030c)
AP SWREV: B:2 K:2 S:2
and a bunch of other info (DID, LOT_ID, CHIP_ID, nAsv_TABLE, nAsv_CPUCL0, nAsv_CPUCL1, nAsv_G3D, nAsv_MIF, nAsv_INT, nAsv_CAM_DISP, nAsv_CP, nAsv_PMIC, nAsv_PMIC_CP, nAsv_FSYS, product_line, asb_version, ids_big, ids_g3d, PMIC_ID, LPDDR4 manufacturer, LPDDR4 process ver, LPDDR3 size)
and anything I try to flash (i tried all files from DBT XXU2, also individual files like just BL/AP/CP/CSC and even individual imgs like sboot, boot, recovery, system, cache) and always the same message All binaries are not allowed to be flashed due to KG Locked.
Is my phone really bricked ? Anybody have any tips on what should I do ? I searched for 2 days for any solution and didn't find anything specific for N960F and solutions for other models didn't work, also nothing comes up on searches on KG STATE :crying:
Click to expand...
Click to collapse
Hello moromindful,
did you ever find any solution to your problem?

besmirgogu said:
Hello moromindful,
did you ever find any solution to your problem?
Click to expand...
Click to collapse
unfortunately no do you know a solution ? or are you in the same situation ?

moromindful said:
unfortunately no do you know a solution ? or are you in the same situation ?
Click to expand...
Click to collapse
same situation :/

besmirgogu said:
same situation :/
Click to expand...
Click to collapse
Maybe someone who has a solution will see this post now that it is bumped up.
I tried a whole lot of different things all ended in the same problem. All binaries are not allowed to be flashed due to KG Locked.

moromindful said:
Hello samsung gurus! I think I've bricked my phone
A few days ago I tried flashing a custom rom (didn't even get to that part but that was my goal).
I was on DBT XXU2CSA2 with XXU2CRTL so I tried flashing other stock roms (only XXU2) via download mode with Odin 3.13.1 and it didn't work it said something like Custom binaries are not allowed to be flashed due to KG locked (BOOTLOADER).
Then I entered recovery and made a factory reset and selected reboot to bootloader and when I tried to flash a rom (stock XEU XXU2ARJ1) it worked ... now I went and enabled the developer mode ... checked OEM Unlock which restarted my phone ... enabled usb debugging because I was preparing for flashing twrp.
Put the phone in recovery and choose reboot to bootloader after that I flashed twrp and then it booted into it.
I was going to flash Dr.Ketan rom and after I downloaded the files I saw that there was a file BL_N960FXXU2CSA2_CP_N960FXXU2CRLT_extract_this_first.zip so I thought that I need to flash that first so I rebooted my phone from twrp pressed vol down + bixby which got me directly into download mode and flashed the bl and cp from odin and this is where all ended it didn't work as it said :
All binaries are not allowed to be flashed due to KG Locked. (RADIO)
And when I restarted my phone the only thing that appears on the screen is: Custom binary blocked due to remaining installment balance. Even when I plug the charger in I get this message and no charger animation So now I can't boot intro recovery because I flashed twrp .. and when I boot in download mode anything that I try to flash ends with the message:
All binaries are not allowed to be flashed due to KG Locked.
When I boot in download mode I get the following details:
PRODUCT NAME: SM-N960F
CURRENT BINARY: Custom
KG STATE: LOCKED
FRP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
CCIC = MAX77705 hw: 3 main: 30
WARRANTY VOID: 1 (0x030c)
AP SWREV: B:2 K:2 S:2
and a bunch of other info (DID, LOT_ID, CHIP_ID, nAsv_TABLE, nAsv_CPUCL0, nAsv_CPUCL1, nAsv_G3D, nAsv_MIF, nAsv_INT, nAsv_CAM_DISP, nAsv_CP, nAsv_PMIC, nAsv_PMIC_CP, nAsv_FSYS, product_line, asb_version, ids_big, ids_g3d, PMIC_ID, LPDDR4 manufacturer, LPDDR4 process ver, LPDDR3 size)
and anything I try to flash (i tried all files from DBT XXU2, also individual files like just BL/AP/CP/CSC and even individual imgs like sboot, boot, recovery, system, cache) and always the same message All binaries are not allowed to be flashed due to KG Locked.
Is my phone really bricked ? Anybody have any tips on what should I do ? I searched for 2 days for any solution and didn't find anything specific for N960F and solutions for other models didn't work, also nothing comes up on searches on KG STATE :crying:
Click to expand...
Click to collapse
Just for my understatement : You flashed a custom ROM via Odin ?
Are you german (because DBT)?

amorosa said:
Just for my understatement : You flashed a custom ROM via Odin ?
Are you german (because DBT)?
Click to expand...
Click to collapse
I am not german. I bought the phone from a friend who lives in Germany.
I flashed via Odin.

besmirgogu said:
same situation :/
Click to expand...
Click to collapse
Did you find a solution ? I have found that the only way would be to change the mother board :|

moromindful said:
Did you find a solution ? I have found that the only way would be to change the mother board :|
Click to expand...
Click to collapse
unfortunately I was told the same thing. I simply gave up...

I have a phone, same your phone: KG STATE: LOCKED My phone is A205F . Can you help me, any one?

https://techshali.com/unbrick-galaxy-note-9/

N960F DS - Custom binary blocked by FRP Lock even after stock firmware flash

Hello All,
Device always flashed with stock DT Germany firmware. A couple of months back I toggled OEM Unlocking (off-on-off) by mistake and next morning device reboots stating "Custom binary blocked by FRP Lock", single red line on top of screen, no other information.
I have tried to flash stock DT Germany firmware several times.Process through ODIN goes fine and completes successfully but phone reboots again in "Custom Binary blocked by FRP Lock".I can only access download mode, no other modes are available (not even recovery)
Below I have attached some screen shots of download mode and ODIN process.
https://drive.google.com/open?id=10aWMWozVCweBe3UTch9PBvvw6fboYjEQ
I have tried several combination files and all have failed.
I hope anyone has faced and sorted this out
Regards

are flashing the same firmware which was on you phone? If not then try the same firmware. Because that is the only reason i think is not resetting the FRP lock.

Munawar Mehmood said:
are flashing the same firmware which was on you phone? If not then try the same firmware. Because that is the only reason i think is not resetting the FRP lock.
Click to expand...
Click to collapse
Hello Munawar,thank you for your reply. I tried to flash same stock firmware which was on phone at the time and it failed with "sw rev check fail(bootloader) device 3 binary 2". I guess this happens because last night I flashed July 2019 stock firmware (ODIN passed it successfully) and bootloader does not allow an older version. I tried with February firmware, March firmware same problem.
What I have noticed is that if I uncheck auto-reboot (ODIN) and flash latest stock AP is passes successfully and on device (download mode) CURRENT BINARY states "Samsung Official" but when I try to reboot it goes back to 'Custom binary blocked by FRP Lock' and CURRENT BINARY switches back to CUSTOM.

besmirgogu said:
Hello Munawar,thank you for your reply. I tried to flash same stock firmware which was on phone at the time and it failed with "sw rev check fail(bootloader) device 3 binary 2". I guess this happens because last night I flashed July 2019 stock firmware (ODIN passed it successfully) and bootloader does not allow an older version. I tried with February firmware, March firmware same problem.
What I have noticed is that if I uncheck auto-reboot (ODIN) and flash latest stock AP is passes successfully and on device (download mode) CURRENT BINARY states "Samsung Official" but when I try to reboot it goes back to 'Custom binary blocked by FRP Lock' and CURRENT BINARY switches back to CUSTOM.
Click to expand...
Click to collapse
your device wasint logged out of google/samsung b4 reset.
dont know where or how you got it but thats what FRP lock is.. also regardless of if you think you flash the "same" firmware as phone was on, i suspect that you did in fact not know which FW it was on. because the message you are getting:
"sw rev check fail(bootloader) device 3 binary 2"
means you are flashing old firmware on a device which has a new bootloader than the one you are trying to flash.
all in all, searching on xda would have provided the information you are seeking.
now flash back stock firmware from July or August 2019.

bober10113 said:
your device wasint logged out of google/samsung b4 reset.
dont know where or how you got it but thats what FRP lock is.. also regardless of if you think you flash the "same" firmware as phone was on, i suspect that you did in fact not know which FW it was on. because the message you are getting:
"sw rev check fail(bootloader) device 3 binary 2"
means you are flashing old firmware on a device which has a new bootloader than the one you are trying to flash.
all in all, searching on xda would have provided the information you are seeking.
now flash back stock firmware from July or August 2019.
Click to expand...
Click to collapse
@bober10113, thank you for your explanation...
I have just tried to flash (again) the following stock firmware (DT Germany-July 2019)
AP_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship_meta_OS9.tar
BL_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship.tar
CP_N960FXXS3CSG1_CP13173080_CL16141281_QB24586509_REV00_user_low_ship.tar
CSC_OMC_ODX_N960FODX3CSF3_CL16070506_QB24108956_REV00_user_low_ship.tar
I did use Odin3 v3.13.3...
Behaviour is the same:
ODIN completes successfully and it claims PASS in green, device tries to reboot and throws black screen with "Custom binary blocked by FRP Lock"
I will try DT Germany-August 2019 or a SAMMOBILE August version as well but I would expect the same behavior as I have tried during all these months.
I also tried nand erase and Re-partition by extracing PIT file from CSC file above
if anything else comes to mind please let me know...

besmirgogu said:
@bober10113, thank you for your explanation...
I have just tried to flash (again) the following stock firmware (DT Germany-July 2019)
AP_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship_meta_OS9.tar
BL_N960FXXS3CSFC_CL16141281_QB24489477_REV00_user_low_ship.tar
CP_N960FXXS3CSG1_CP13173080_CL16141281_QB24586509_REV00_user_low_ship.tar
CSC_OMC_ODX_N960FODX3CSF3_CL16070506_QB24108956_REV00_user_low_ship.tar
I did use Odin3 v3.13.3...
Behaviour is the same:
ODIN completes successfully and it claims PASS in green, device tries to reboot and throws black screen with "Custom binary blocked by FRP Lock"
I will try DT Germany-August 2019 or a SAMMOBILE August version as well but I would expect the same behavior as I have tried during all these months.
I also tried nand erase and Re-partition by extracing PIT file from CSC file above
if anything else comes to mind please let me know...
Click to expand...
Click to collapse
why are your files named . tar?
i think your not even flashing anything. how long does it take to flash?

bober10113 said:
why are your files named . tar?
i think your not even flashing anything. how long does it take to flash?
Click to expand...
Click to collapse
actually files are in ".tar.md5" but I did not include this extension, I am sorry for the confusion.
last flash took around 4minutes
Should they be in another format?

besmirgogu said:
actually files are in ".tar.md5" but I did not include this extension, I am sorry for the confusion.
last flash took around 4minutes
Should they be in another format?
Click to expand...
Click to collapse
nah i was just wondering if they acctualy were real stock unaltered firmware files.
but anyways. that should have fixed it. so i dont know what to tell you. search around i guess

bober10113 said:
nah i was just wondering if they acctualy were real stock unaltered firmware files.
but anyways. that should have fixed it. so i dont know what to tell you. search around i guess
Click to expand...
Click to collapse
ok, thank you for your help...

well start from scratch.
clean your phone port with a tooth brush gently.
remove samsung drivers, then install latest samsung drivers again. and change usb port (version 2.0) and usb cable. because sometimes damage cable cause this issue. run odin as administrator (right click on odin icon and select run as administrator) and then select nand erase and pit file and flash latest stock firmware.

Munawar Mehmood said:
well start from scratch.
clean your phone port with a tooth brush gently.
remove samsung drivers, then install latest samsung drivers again. and change usb port (version 2.0) and usb cable. because sometimes damage cable cause this issue. run odin as administrator (right click on odin icon and select run as administrator) and then select nand erase and pit file and flash latest stock firmware.
Click to expand...
Click to collapse
I tried as per above guidelines. stock firmware flashed:
AP_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship_meta_OS9.tar.md5
BL_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship.tar.md5
CP_N960FXXS3CSG2_CP13219698_CL16141281_QB24670232_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM3CSG3_CL16141281_QB24861261_REV00_user_low_ship.tar.md5
ODIN passed it successfully. Device in download mode says CURRENT BINARY: Custom and of course "Custom binary blocked by FRP lock"

besmirgogu said:
I tried as per above guidelines. stock firmware flashed:
AP_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship_meta_OS9.tar.md5
BL_N960FXXS3CSG5_CL16141281_QB25130720_REV00_user_low_ship.tar.md5
CP_N960FXXS3CSG2_CP13219698_CL16141281_QB24670232_REV00_user_low_ship.tar.md5
CSC_OMC_OXM_N960FOXM3CSG3_CL16141281_QB24861261_REV00_user_low_ship.tar.md5
ODIN passed it successfully. Device in download mode says CURRENT BINARY: Custom and of course "Custom binary blocked by FRP lock"
Click to expand...
Click to collapse
you are doing something wrong. as stock firmware is the only option to remove custom binary error. try someone else PC and data cable.

Munawar Mehmood said:
you are doing something wrong. as stock firmware is the only option to remove custom binary error. try someone else PC and data cable.
Click to expand...
Click to collapse
I am trying to understand which of the steps I am doing wrong. I managed to successfully flash a Galaxy Note 8 today so I know that laptop, cable and steps followed are fine.
What seems strange to me is that on this Galaxy Note 9 ODIN completes successfully in 2 min and 14 seconds but every time phone states CURRENT BINARY: Custom making me think that device is not being flashed at all. Any ideas how to confirm this?

Did you flash anything onto this device that would cause a "Custom" status? For one im not sure how you managed to even get a Custom Binary without setting the Warranty Bit. 2nd I noticed "Eng Mode: Dev Device" in Download Mode. And thirdly How do you manage to tick OEM Unlocking Off, On and then back Off accidentally? Changing the OEM Unlocking setting requires a Factory Reset each time.

last1youlove said:
Did you flash anything onto this device that would cause a "Custom" status? For one im not sure how you managed to even get a Custom Binary without setting the Warranty Bit. 2nd I noticed "Eng Mode: Dev Device" in Download Mode. And thirdly How do you manage to tick OEM Unlocking Off, On and then back Off accidentally? Changing the OEM Unlocking setting requires a Factory Reset each time.
Click to expand...
Click to collapse
I have never flashed anything other than stock DT firmware on this device (multiple times). It was never rooted...
It seems strange to me as well that Warranty bit is 0 while it says "Current Binary: Custom".
It says "Eng Mode: Dev Device" as this is a testing device that Samsung releases to its partners (mainly Telco Partners) for testing and development, so it never was a commercial unit for sale.
OEM Unlocking was off and I remember ticking it "on" by mistake as I did not intend to perform any flashing at the time. As I can recall I left it on and next morning phone reboots claiming "Custom binary blocked by FRP Lock". I would bet that I left it on but in download mode you can see that it says "OEM LOCK: ON" which I guess means "OEM UNLOCK: OFF".

besmirgogu said:
I have never flashed anything other than stock DT firmware on this device (multiple times). It was never rooted...
It seems strange to me as well that Warranty bit is 0 while it says "Current Binary: Custom".
It says "Eng Mode: Dev Device" as this is a testing device that Samsung releases to its partners (mainly Telco Partners) for testing and development, so it never was a commercial unit for sale.
OEM Unlocking was off and I remember ticking it "on" by mistake as I did not intend to perform any flashing at the time. As I can recall I left it on and next morning phone reboots claiming "Custom binary blocked by FRP Lock". I would bet that I left it on but in download mode you can see that it says "OEM LOCK: ON" which I guess means "OEM UNLOCK: OFF".
Click to expand...
Click to collapse
so this is the problem, you are flashing commercial firmware on testing device to rectify the custom lock. try flashing combination firmware. in this guide is a link to download combination firmware. it is official combination firmware to solve device problems.

Munawar Mehmood said:
so this is the problem, you are flashing commercial firmware on testing device to rectify the custom lock. try flashing combination firmware. in this guide is a link to download combination firmware. it is official combination firmware to solve device problems.
Click to expand...
Click to collapse
I managed to flash COMBINATION_FAC_FA81_N960FXXU3ASF1_BoxWares.tar.md5. Phone tries to reboot showing corrent model but on top of screen it says "Boot image signature check fail!!!" and "Reboot to avoid Warranty bit set!!!"
In download mode CURRENT BINARY:Custom and SYSTEM STATUS:Custom
I have added below a couple of screen shots of the situation now:
https://drive.google.com/open?id=1lwbblCDLKnvDkyBMtlsOOhH_F1c4HpeJ

i have once again gone through the entire thread and i see that you mention odin version 3.13.3, while the latest version of odin is 3.13.1. and i am using odin version 3.13.1. try this specific version of odin. and flash combination firmware. it seems from latest screen shot that your phone is not flashing any firmware. it just shows progress on pc but on phone it is not happening at all. try the odin version i mentioned.

My working theory is that because this is a testing device it's marking any firmware that isn't the specific engineering firmware the device shipped with as a "Custom Binary" you wouldn't be able to flash official releases. (Including Combination Firmware) You would probably need to return the device to the manufacturer or provider and request that the original operating system image be restored.
However please take this with a grain of salt. I'm not certain this is the case.

last1youlove said:
My working theory is that because this is a testing device it's marking any firmware that isn't the specific engineering firmware the device shipped with as a "Custom Binary" you wouldn't be able to flash official releases. (Including Combination Firmware) You would probably need to return the device to the manufacturer or provider and request that the original operating system image be restored.
However please take this with a grain of salt. I'm not certain this is the case.
Click to expand...
Click to collapse
you sir are making alot of sense.