Database Develop

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.

RMM state: prenormal after OEM unlock on Android 9.0

Hello!
Got a strange situation: set up new Note9, updated it to Pie, connected to Wi-Fi and did OEM unlock instantly rebooting to Odin mode to flash TWRP, but instead of this I got RMM state: prenormal message (should be RMM state: checking in Pie) and KG state : checking. Booted back in OS, set it up and see OEM unlock active in Development options. Unlocked lots of samsung devices - but they are all always got me RMM checking and let flash TWRP instantly in PIE. Is this some new security feature or its because I updated to PIE from Oreo and still have to wait 7 days for unlock?

+1 waitting

Narkozzz said:
Hello!
Got a strange situation: set up new Note9, updated it to Pie, connected to Wi-Fi and did OEM unlock instantly rebooting to Odin mode to flash TWRP, but instead of this I got RMM state: prenormal message (should be RMM state: checking in Pie) and KG state : checking. Booted back in OS, set it up and see OEM unlock active in Development options. Unlocked lots of samsung devices - but they are all always got me RMM checking and let flash TWRP instantly in PIE. Is this some new security feature or its because I updated to PIE from Oreo and still have to wait 7 days for unlock?
Click to expand...
Click to collapse
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.
Click to expand...
Click to collapse
The problem is RMM prenormal state even after clean flash of stock rom and oem unlock enabled. I cant flash anything non-signed. With all respect to dr.ketan I have mine experience that never failed before - RMM checking always appear after unlock on Pie. So I asking people who could have same issue - will it change from prenormal to checking in 7 days or I better flash Oreo and wait 168 hours?

Narkozzz said:
The problem is RMM prenormal state even after clean flash of stock rom and oem unlock enabled. I cant flash anything non-signed. With all respect to dr.ketan I have mine experience that never failed before - RMM checking always appear after unlock on Pie. So I asking people who could have same issue - will it change from prenormal to checking in 7 days or I better flash Oreo and wait 168 hours?
Click to expand...
Click to collapse
fine dont read and follow the guide to flash his root oem fix root v5
sheesh
here are some more details since you are new to note 9.
here an other zip that does partially what ketans does:
https://1drv.ms/u/s!AhXVLDDj8g3AgrxVEeICKZil9BIAUA?e=kpfiM9
it has no kernel nor magisk.
ketan has a kernel and magisk AND rmm state fix that should make device be able to boot while on custom recovery as the kernel needs to be patched in order to boot.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
the real problem was not reading the guides section attentively. check for dr.ketans guide and follow it through.
you should be using method 1 in the guide.
and again follow it from a to z.
now flash back stock firmware and start the procedure again.
Click to expand...
Click to collapse
bober10113 said:
fine dont read and follow the guide to flash his root oem fix root v5
sheesh
here are some more details since you are new to note 9.
here an other zip that does partially what ketans does:
https://1drv.ms/u/s!AhXVLDDj8g3AgrxVEeICKZil9BIAUA?e=kpfiM9
it has no kernel nor magisk.
ketan has a kernel and magisk AND rmm state fix that should make device be able to boot while on custom recovery as the kernel needs to be patched in order to boot.
Click to expand...
Click to collapse
Thank you for trying to help me, friend. But you misses the core thing - to flash anything mentioned in dr.ketan's guide I have to flash TWRP first. But I cant flash TWRP since I have RMM state prenormal mode alongside with unlocked bootloader. Even after reflash of stock rom. So the only question in my situation is: will RMM state change after 168 hours wait on Pie, or I need to flash Oreo rom first and wait. I am not new neither to Note9 unlocking, not to Samsung devices and have all needed tools to fix OEM and RMM issue AFTER I will get a chance to flash TWRP.

Narkozzz said:
Thank you for trying to help me, friend. But you misses the core thing - to flash anything mentioned in dr.ketan's guide I have to flash TWRP first. But I cant flash TWRP since I have RMM state prenormal mode alongside with unlocked bootloader. Even after reflash of stock rom. So the only question in my situation is: will RMM state change after 168 hours wait on Pie, or I need to flash Oreo rom first and wait. I am not new neither to Note9 unlocking, not to Samsung devices and have all needed tools to fix OEM and RMM issue AFTER I will get a chance to flash TWRP.
Click to expand...
Click to collapse
flash stock. boot to home screen make it check for updates in the software menu once. check dev tool if OEM unlock is there. if it is a unlocked flash twrp. and boot directly to recovery after odin finishes. in recovery format data in wipe menu and type yes. go to reboot menu and choose reboot to recovery. flash ketans oem root fix v5 in aroma setup choose to flash kernel and magisk.
ive had your issue before. its not complicated. just do what i said if your oem unlock is there and unlocked. if its vanished and want it to appear then there are guides to make it appear instead of waiting.
also do you want oreo or pie? ketan has both. just read..

You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.

Narkozzz said:
You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.
Click to expand...
Click to collapse
well if you dont try as i said of course youll never know.
again, i had your issue and alot of people as well. please use xda search feature and read. if not then dont post for help if you dont want help.

Narkozzz said:
You are not listening: I flashed stock; I connected to WiFi; I do see OEM unlock enabled in Development Options; Still I have RMM state prenormal in Odin mode and cant flash TWRP.
Click to expand...
Click to collapse
I also have the problem, but with the S10.
OEM activation active, even reactivated in download mode, so OEM activation is gray. Even the trick with the 8 days did not help - it remains prenormal.

bober10113 said:
the waiting periode is not the issue. if oem unlock is there then no wait was needed.
you should be using method 1 in the guide.
Click to expand...
Click to collapse
Hello, do you have a link for the manual?
Have been looking for a long time and geffen nothing.
Maybe I will continue with the instructions to get the "prenormal" away

bininga59 said:
Hello, do you have a link for the manual?
Have been looking for a long time and geffen nothing.
Maybe I will continue with the instructions to get the "prenormal" away
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143

I am in the same situation, the rmm state prenormal still continues
even when I have the OEM unlocked, in fact I tried to do it through the chimera
program, but for having the June android security patch (CSF2)
the chimera friends commented to me that for that reason I could not do the
unlocking of rmm through their program, they told me that they worked on a
solution for it, but they did not give me an estimate of time, I guess we will
have to wait for a solution from them, since searching and reading most of the post,
none worked for me, I'm stuck in not being able to flash TRWP, so I can't really do anything.
I hope someone finds a solution or that through the chimera program, we can correct that problem.

I'm facing same problem on sm-a730f, the rmm state prenormal still active
even when I have the OEM unlocked

Same problem here, i'm using a brazilian Samsung galaxy Note 9 N9600 retail version

Same situation here i have galaxy s9 exynos

RMM state prenormal fix for non-US phones
@bober10113 et al, specially non-US folks
I guess these guys are suffering the same as me, it is exactly like what @Narkozzz said. RMM state prenormal (even with OEM already unlocked!!!) won't allow for flashing one single thing other than official binaries e.g. TWRP without which we can do nothing (the fixes are only prevention, not remedying).
Skimming through Samsung international forums abroad and other websites I saw the solution consists in installing the SIM card, flashing stock with Odin again, and then keeping the cellphone, the simcard and the mobile data turned on constantly. Eventually after 7 days, on in some cases more than a month, that state will reset back and we will then be able to flash TWRP and the RMM bypass, plus noverity etc. etc.
Ketan also mentioned that in the comments in his topic, although he did not mention specifically about keeping the simcard together with mobile data enabled during all the time
I'm about to flash mine now and wait with everything enabled, following that solution.
Will report back in here after a while
Cheers!

active usb debugging and active oem, the same happens in note 9, waiting for your experience

For what it's worth, I'm going to share what I've done; since it seems like I've somehow just stumbled through the same issue on my note 9, without having to wait any substantial amount of time. Hopefully it's of some use to someone.
I originally had N960FXXU3CSF9 (rooted with TWRP installed) on my Exynos Note 9; flashed stock N960FXXS3CSG5 using Odin, got about half way through the new device setting up process then black screen with "Only official released binaries are allowed to be flashed" message.
Me rambling about my fails
After the initial 30 minutes of panic and swearing, got the phone to download mode (Volume Down + Bixby, plug in USB from PC), then various combinations of trying to flash the same stock N960FXXS3CSG5 rom, TWRP, trying to install no-verity-opt-encrypt and Magisk-v18.0. The only change I noticed was RMM state sometimes seems to be stuck on "checking" instead of "Prenormal" while in download mode sometimes; either way, all ends with the same "Only official released binaries are allowed to be flashed" brick.
Last ditch attempt that worked for me:
(from RMM msg brick)
- Volume Down + Bixby, plug in USB from PC to Download mode
- Flashed the old N960FXXU3CSF9 stock rom with Odin;
- Turned phone off after 1st reboot after ^;
- Volume Down + Bixby, plug in USB from PC to Download mode
- Flashed twrp-3.2.3-0-crownlte_UNOFFICIAL.tar.md5
- Held down Volume Up + Bixby + Power before reboot from ^, to boot straight to TWRP recovery
- Transferred N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip & Magisk-v18.0.zip from PC to external SD card
- From TWRP, Wipe - Format Data - "yes"; after format is done, press back to first TWRP page
- Install N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip
- Install Magisk-v18.0.zip
- Wipe Dalvik Cache
- Reboot to System
More rambling
it then took a few minutes with boot img before "optimizing apps" (I assume this is code for Samsung black magic and murdering imaginary orphans?) then eventually I got to enter my details through the new device set up process... for the 10th time today. So far it's been about 6hrs since I've put all my apps back, in developer options OEM unlocking is off, but
I have root access back, and everything seems to be fine.
Sorry that I kept jumping between tenses and waffled on a bit there; it's been a long 20 hrs of reading forums, articles, hand cramps death gripping phone buttons and bashing head against desks. Hope this is useful to someone, I'm off to find 2 tin cans and some string.

Need help for n9... Prenormal

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.

[HELP] A6+ (A605F) My Phone hard bricked, tried everything, still bootlooping.

Guys I have this galaxy a6 plus and suddenly it started bootlooping for two days now im trying to fix it.
i tried : flashing new full rom from sammobile, flashing only in AP. I also tried flashing recovery but always get blocked by FAP LOCK
the only thing i can do with the phone is go to download mode. i cant even go to recovery.
the information on download mode :
Code:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-A605F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
OEM LOCK: ON
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLED (CSB)
AP SWREV: S1, T1, R1, A4, P4
AP SWREV: K 4, S 4
SECURE DOWNLOAD : ENABLE
DID : 009aba66fcd3
download mode !!
please help me with this guy i really dont want to lose the phone.

how about bringing it to samsung service center?

What have you done before the problem?

JasonS. said:
What have you done before the problem?
Click to expand...
Click to collapse
This all started from flashing broken recovery
I had bootloop, and I can't find any way to fix this
so I tried to flash new firmware, but it always goes to recovery mode
I couldn't enter download mode, so I brought to samsung service center

tmvkrpxl0 said:
This all started from flashing broken recovery
I had bootloop, and I can't find any way to fix this
so I tried to flash new firmware, but it always goes to recovery mode
I couldn't enter download mode, so I brought to samsung service center
Click to expand...
Click to collapse
Weird... should still be able to enter download mode. From there, flash original firmware on everything (AP, BL, CSC, etc.)

its gonna be late answer but u should run odin as an administor and flash latest rom.

joker.lg said:
its gonna be late answer but u should run odin as an administor and flash latest rom.
Click to expand...
Click to collapse
To expand on that, make sure that your phone is detected by odin. Run odin as administrator and install the samsung USB drivers as well.
Then, on connect, odin should show "added" for your phone.
From there, fully flash a stock rom (BL,AP,CP,CSC) with a version equal to or better than what you had before, ideally the one made for your country and carrier. Beware that if you update to a late pie rom, you can NOT go back to oreo.

joker.lg said:
its gonna be late answer but u should run odin as an administor and flash latest rom.
Click to expand...
Click to collapse
does that do anything

Note 9 soft bricked?

Hi! I've tried following dr.ketan's post on rooting a Note 9 with the first method ("(Guide)Root +Busybox + OEM Fix + EFS backup Note 9 N960F/FD/N Exynos only").
After that I've flashed RomAur via TWRP, booted up and while setting up my account the screen became black with the message "only official released binaries are allowed" . I've then tried to flash the stock firmware via Odin but on the screen of my phone I get a "SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1" error.
Odin seemed stuck so I unplugged my phone and then got a screen saying "An error has occured updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
My phone's a N960F/DS

After further research I've come to the conclusion that:
1) SW REV CHECK FAIL (BOOTLOADER) DEVICE 4 BINARY 1 means the firmware I was trying to flash was too old and Samsung decided that downgrading isn't an option anymore.
2) I'm unable to flash anything else besides Samsung official firmware for a 7 or more days because of a Knox Guard (RMM/KG state prenormal). So reinstalling any custom recovery to then flash a new Rom can't be done since there's no way to bypass this time period on Pie.
I did end up flashing stock but I can't mod my phone until the kg state goes back to normal or checking

I've tried waiting for 168 hours twice since the last post. KG State won't change from prenormal. I should mention that my OEM unlock option is available but I can't flash anything besides Samsung binaries. Last week I've flashed TWRP despite the KG State not changing and I got the same "only official released binaries are allowed" error followed by a red fail box in ODIN. At this point I have no idea how to fix it. Does anyone have any suggestion?

I've downloaded the latest stock (N960FXXU4DSLB) and installed it. After that it looks like the prenormal state went away. Immediately I've toggled the OEM Unlock option, waited for the factory reset to be done and checked to see if the toggle was still there. The OEM unlock option works just like before BUT I've successfully installed geiti94's latest TWRP (3.2.3 ATM). Flashing RMM-State_Bypass_Mesa_v2.zip no-verity-opt-encrypt-6.0.zip and Magisk 20.2 seem to be able to get root working but there are some weird bugs:
- can't set up any security measure such as a pin, patter or biometrics
- if I try to log into my Samsung account I get a "processing failed" pop up
- restarting my phone causes it to bootloop