Related
Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet.I Dont Know if it Will Work on Other Firmware. I Tried On 6.0.1
"CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip" Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
Download And Install the Samsung USB Driver in your PC.
Extract the CF-Auto-Root files in your PC.
Switch off your Mobile.Enter into Download mode->Volume Down+Home+Power Buttons.
After entering into Download Mode it will say Warning Press Volume Up button to continue.
Connect Your Mobile With PC via USB Cable.
Launch Odin Application.It Will Show the message added.If you did not get this message Repeat the above steps.
After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file Select it.Tick the Auto reboot.
Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
Reboot again.
You can See the Superuser after the Reboot in your Applications list.
This will trip Knox correct?
Sent from my SM-G920T using Tapatalk
I am also curious will this trip Knox?.. I'm assuming anything involving odin is an automatic yes?.
Yes All Rooting trips knox
Do you need to turn on OEM unlocking?
It failed for me did all the steps.
Copied and pasted the OP and adding my own notes:
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
ktrinh4213 said:
Copied and pasted the OP and adding my own notes:
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Click to expand...
Click to collapse
Been searching all day and found this and am curious if it works on the EPF1 build of the s6. I keep hearing that my bootloader is locked and it will brick my device so just wanted some confirmation that someone has done this with the same phone and build that i have and that it works without messing anything up. thanks in advance
kenpachi100 said:
Been searching all day and found this and am curious if it works on the EPF1 build of the s6. I keep hearing that my bootloader is locked and it will brick my device so just wanted some confirmation that someone has done this with the same phone and build that i have and that it works without messing anything up. thanks in advance
Click to expand...
Click to collapse
It works, because I was on stock before I rooted. You have to unlock your OEM bootloader using steps 5 and 6 that I mentioned, or you will soft-brick your phone.
ktrinh4213 said:
It works, because I was on stock before I rooted. You have to unlock your OEM bootloader using steps 5 and 6 that I mentioned, or you will soft-brick your phone.
Click to expand...
Click to collapse
So youve done this on your phone?
I have already toggled the oem unlock option but i was told by samsung support that it doesnt unlock the bootloader.
Sorry not trying to be annoying i just really dont wanna mess my phone up. Just to be certain my s6 is stock ota 6.0.1 from tmobile with the EPF1 build.
kenpachi100 said:
So youve done this on your phone?
I have already toggled the oem unlock option but i was told by samsung support that it doesnt unlock the bootloader.
Sorry not trying to be annoying i just really dont wanna mess my phone up. Just to be certain my s6 is stock ota 6.0.1 from tmobile with the EPF1 build.
Click to expand...
Click to collapse
I know for sure it works because I did it the wrong way, and found out the right way. When you Unlock OEM, it unlocks your FRP (Factory Reset Protection). Without that being unlocked, you will be in a bootloop with the Samsung splash screen with the words FRP Locked (or something similar) at the top left hand corner until you flash the stock ROM from Sammobile via Odin.
Without following the steps I prescribed, you will soft-brick your phone, and ultimately, you will lose all data and information saved on your phone anyway. Unlocking it will remove the FRP lock so that when you reboot after rooting with CF-Auto-Root, you can log into your phone as usual (fingerprint, password, PIN, etc.) rather than being met with that Samsung splash screen.
ktrinh4213 said:
I know for sure it works because I did it the wrong way, and found out the right way. When you Unlock OEM, it unlocks your FRP (Factory Reset Protection). Without that being unlocked, you will be in a bootloop with the Samsung splash screen with the words FRP Locked (or something similar) at the top left hand corner until you flash the stock ROM from Sammobile via Odin.
Without following the steps I prescribed, you will soft-brick your phone, and ultimately, you will lose all data and information saved on your phone anyway. Unlocking it will remove the FRP lock so that when you reboot after rooting with CF-Auto-Root, you can log into your phone as usual (fingerprint, password, PIN, etc.) rather than being met with that Samsung splash screen.
Click to expand...
Click to collapse
So you were on 6.0.1 stock ota when you did it?
Also will doing it this way wipe my data or just install root?
Also also would i just flash twrp via odin after doing this or..?
kenpachi100 said:
So you were on 6.0.1 stock ota when you did it?
Also will doing it this way wipe my data or just install root?
Also also would i just flash twrp via odin after doing this or..?
Click to expand...
Click to collapse
Yes
No, it just installs root.
This does not automatically flash TWRP for you, it's something you have to do yourself.
ktrinh4213 said:
Yes
No, it just installs root.
This does not automatically flash TWRP for you, it's something you have to do yourself.
Click to expand...
Click to collapse
I know it doesnt automatically flash TWRP i was asking how i would flash twrp afterwards. I guess it would have to be odin since you cant flash it from the phone without a custom recovery. Also, again just trying to clarify, your build number had EPF1 when you did this also?
kenpachi100 said:
I know it doesnt automatically flash TWRP i was asking how i would flash twrp afterwards. I guess it would have to be odin since you cant flash it from the phone without a custom recovery. Also, again just trying to clarify, your build number had EPF1 when you did this also?
Click to expand...
Click to collapse
Go to the TWRP website and find the latest build number, or download the TWRP Manager app on the Play Store and you can download and flash it from there.
Yes, my ROM was STOCK OTA.
ktrinh4213 said:
Go to the TWRP website and find the latest build number, or download the TWRP Manager app on the Play Store and you can download and flash it from there.
Yes, my ROM was STOCK OTA.
Click to expand...
Click to collapse
Okay, thanks for answering all my questions and the help!
works like a charm. thanks for sharing!
Will this work for this Build Number which is MMB29K.G920TUVU4EPF1?
php111 said:
Will this work for this Build Number which is MMB29K.G920TUVU4EPF1?
Click to expand...
Click to collapse
Yes it will.
I took the 6.0.1 OTA Update. So is this what I need to do?
First, download 6.0.1 from like the site Sammobile and Flash via ODIN and should I check or uncheck Auto reboot?
Than once I flashed than follow all 13 steps given in post #7 of this thread
Once I followed the 13 steps than flash TWRP? Should I flash via ODIN or recovery? If in ODIN should check or unchecked Auto reboot?
Once I got TWRP than install Super SUPER SU from Play Store
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.
I bought a Note 9 (SM-N960F) second-hand and it turns out it was rooted in the past. I wanted to update the buildprop so that S Health would work so re-rooted the phone, made the necessary changes, which worked fine and then started removing root, TWRP, etc.
I unticked OEM unlock, the phone restarted and now everytime I try to start my phone I get "Custom Binary Blocked by OEM lock" in red and that's it.
I can't access Samsung recovery (Bixby + Vol Down + Power) to re-flash a standard ROM and I cannnot boot into TWRP (Bixby + Vol Up + Power).
Have I bricked it? Is it now a £500 paperweight? Any ideas on a solution?
Your system partition is no longer intact. Of course you should keep the OEM lock off.
Have you tried entering download mode by holding vol down + bixby while plugging your cable in, while the phone is powered off?
Thank you! That worked
If you had searched you would have found that you can get S Health to work by downloading and installing an earlier version set it up, then update to the latest version. I had the same problem with my S8+. Just can't remember what earlier version to download but Google is your friend there.
Was no need to re root and edit build prop.
Cheers.
You saved me... Thank you sir.
Hello, I am also facing the same issue in Samsung S9 which I have bought from the Netherlands. I have bought a brand new Samsung s9 phone then I flushed Custom ROM and then I Off the OEM Unlocking and now when I restarted it, it's showing "Custom Binary Blocked by OEM lock" in red. I tried to install the stock ROM (version number PDA G960FXXU2BRJ8 and CSC G960FOXM2BRJ4) via Odin, but it's showing error while I install this via Odin "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY:2"
If I download Samsung firmware for the Galaxy S9 SM-G960F for the Netherlands, it's showing many carriers options like: Netherlands (PHN), Netherlands (Vodafone) VDF, Netherlands (Ben NL) DNL, Netherlands (T-Mobile) TNL. Which version I have to select from these before I downloaded Netherlands (PHN). I bought this S9 phone without any telecom contract (SIM Free).
Please help me out from this issue. Am I installing the right version of the stock ROM?
akshay9090 said:
Hello, I am also facing the same issue in Samsung S9 which I have bought from the Netherlands. I have bought a brand new Samsung s9 phone then I flushed Custom ROM and then I Off the OEM Unlocking and now when I restarted it, it's showing "Custom Binary Blocked by OEM lock" in red. I tried to install the stock ROM (version number PDA G960FXXU2BRJ8 and CSC G960FOXM2BRJ4) via Odin, but it's showing error while I install this via Odin "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY:2"
If I download Samsung firmware for the Galaxy S9 SM-G960F for the Netherlands, it's showing many carriers options like: Netherlands (PHN), Netherlands (Vodafone) VDF, Netherlands (Ben NL) DNL, Netherlands (T-Mobile) TNL. Which version I have to select from these before I downloaded Netherlands (PHN). I bought this S9 phone without any telecom contract (SIM Free).
Please help me out from this issue. Am I installing the right version of the stock ROM?
Click to expand...
Click to collapse
1- this is note 9 forums
2- you are attempting to flash OLD firmware on a newer based bootloader phone.
3- search and read.
so just don't flash old firmware. download the newest. search are read about bootloader versions so you don't get the SW REV error again and also search on how or where to download the newest firmware or at least one that matches your bootloader revision.
it happen to my note 9 today and not even let to me to boot into download or recovery, please please anyone can help.
my costum binary blocked by oem lock(j610f)
I flashed the BL and CP, but there is still an OEM lock message after the reset
timshields said:
I bought a Note 9 (SM-N960F) second-hand and it turns out it was rooted in the past. I wanted to update the buildprop so that S Health would work so re-rooted the phone, made the necessary changes, which worked fine and then started removing root, TWRP, etc.
I unticked OEM unlock, the phone restarted and now everytime I try to start my phone I get "Custom Binary Blocked by OEM lock" in red and that's it.
I can't access Samsung recovery (Bixby + Vol Down + Power) to re-flash a standard ROM and I cannnot boot into TWRP (Bixby + Vol Up + Power).
Have I bricked it? Is it now a £500 paperweight? Any ideas on a solution?
Click to expand...
Click to collapse
use FRP Hijacker
Here is the solution :
Download Frija , input your phone model and proper CSC region
e.g. = India = INS
( Make sure to uncheck binary nature and CRC check in settings or it will delete the firmware after download )
extract your downloaded firmware and flash it through odin.
i bought a s10(sm-g973f) but i turn on the oem but still giving error of oem lock
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
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.