Related
Trying to compile as many users who have faced the same issue and to get some data to find a work around.
SM-N950F - Australian (TEL/TEL/TEL) post paid Telstra Note 8.
Waited one week for 'Allow OEM to be unlocked' to appear in Dev Settings.
This is my experience and now have the official binaries issue.
I also got the OEM unlock after one week, this is what happened when trying to install TWRP and Magisk on Stock ROM.
I tried to flash TWRP lost night and that was okay. I decided to hold onto stock and just have TWRP and Magisk at this stage until other roms are a little less buggy. Flashed TWRP. flashed Verity / Magisk, setup phone again and then decided to do a backup in TWRP. When trying to go into TWRP got the message 'Only official released binaries are allowed to be flashed' and then went into a soft brick. Had to restore phone to stock and now OEM unlock has disappeared again, In download mode FRP and OEM lock are both OFF. Tried to reflash TWRP and get the same message - 'Only official released binaries are allowed to be flashed'.
So the plot thickens.
Andysmith71 said:
Trying to compile as many users who have faced the same issue and to get some data to find a work around.
SM-N950F - Australian (TEL/TEL/TEL) post paid Telstra Note 8.
Waited one week for 'Allow OEM to be unlocked' to appear in Dev Settings.
This is my experience and now have the official binaries issue.
I also got the OEM unlock after one week, this is what happened when trying to install TWRP and Magisk on Stock ROM.
I tried to flash TWRP lost night and that was okay. I decided to hold onto stock and just have TWRP and Magisk at this stage until other roms are a little less buggy. Flashed TWRP. flashed Verity / Magisk, setup phone again and then decided to do a backup in TWRP. When trying to go into TWRP got the message 'Only official released binaries are allowed to be flashed' and then went into a soft brick. Had to restore phone to stock and now OEM unlock has disappeared again, In download mode FRP and OEM lock are both OFF. Tried to reflash TWRP and get the same message - 'Only official released binaries are allowed to be flashed'.
So the plot thickens.
Click to expand...
Click to collapse
We are on the same boat bro,
Mine is SM-N950F/DS Singapore (XSP), got on Sep 9th via preorder from Singtel.
But I did not notice if oem unlock option was there when I got the device. Then I tried to flash TWRP last week(oem unlock was there), flashed SuperSU 2.82. When I was configuring an app to modify host(to disable ads), the phone rebooted itself before I was able to flash dm-verity, and went into the bootloop with the same msg 'Only official released binaries are allowed to be flashed' [emoji33]
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
thegreenthief said:
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
Click to expand...
Click to collapse
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
zhengsmall said:
We are on the same boat bro,
Mine is SM-N950F/DS Singapore (XSP), got on Sep 9th via preorder from Singtel.
But I did not notice if oem unlock option was there when I got the device. Then I tried to flash TWRP last week, flashed SuperSU 2.82. When I was configuring an app, the phone rebooted itself before I was able to flash dm-verity, and went into the bootloop with the same msg 'Only official released binaries are allowed to be flashed'
Click to expand...
Click to collapse
Hey mate, maybe you can try the method a few users are going to do now, after another week and when OEM re appears then redo the process but this time don't boot the device. However I see what happened in your case the phone restarted itself when configuring SuperSU.. I've not hear that happening before. Maybe try Magisk if your looking at trying again? Strange it rebooted by itself. Good luck and let us know how you go.
Andysmith71 said:
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
Click to expand...
Click to collapse
It's good we're getting to a point where we can collect data and try different approaches. It was a much darker time when we were all sitting around wondering if/when the OEM Unlock toggle would show up!
Yes, I did a wipe/format prior to flashing Magisk. One thing I haven't been doing is clearing the cache/dalvik following successful flash... is that important? I recall doing that back when I rooted my S7 Edge, but I've not seen or heard about anyone doing it since.
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
krabman said:
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
Click to expand...
Click to collapse
Thanks mate, been reading up there and seen the posts. Looks like Renovate has had most success so far with that method. Looks promising, fingers crossed. I've got another few more days in jail before I get the OEM unlock back.
I don't think anyone has reported a failure yet doing it that way. Still a ways to go on the testing though, It appears folks aren't all that anxious to screw up a good thing once they get up and running. The good news is if ordinary dumbassez like us can get in the smart guys should get something figured out sooner rather than later. Anyhow, good luck, if it's any consolation mine showed up in 5 days...
Andysmith71 said:
Hey mate, maybe you can try the method a few users are going to do now, after another week and when OEM re appears then redo the process but this time don't boot the device. However I see what happened in your case the phone restarted itself when configuring SuperSU.. I've not hear that happening before. Maybe try Magisk if your looking at trying again? Strange it rebooted by itself. Good luck and let us know how you go.
Click to expand...
Click to collapse
Thanks for the suggestion mentioned, but what do you mean by redo the process? Or just switch off and then on the oem unlock toggle when it reappears in 7 days after the first flash(twrp and supersu) followed by a reboot(as only via reboot can I judge if it works)?
In addition, in my case the phone restarted itself when I tried to modify host to disable the annoying ads, not during configuring SuperSU.
Just ended up in the same boat as OP. same version same carrier etc.
hopefully soon the smart ones can figure this out. off to find stock rom and try to get back a working device
AndiF85 said:
Just ended up in the same boat as OP. same version same carrier etc.
hopefully soon the smart ones can figure this out. off to find stock rom and try to get back a working device
Click to expand...
Click to collapse
Hey mate, try the below mentioned method and see if it works.
thegreenthief said:
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
Click to expand...
Click to collapse
Andysmith71 said:
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
Click to expand...
Click to collapse
I will give it a try once oem unlock returns. Hopefully this can be resolved soon. Being in jail sucks. I've tripped Knox so lost Samsung features and no root still so dont have root advantages.
Sent from my SM-N950F using Tapatalk
krabman said:
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
Click to expand...
Click to collapse
Well I got out of Jail yesterday after getting back the OEM unlock for the 2nd time. This time I decided to 'play it safe' until the smart people figure out what the issues are. This method worked perfectly for me and I've now been flashing Viper, flashing extra fonts, doing backups in TWRP and generally using the phone as normal again. The current Renovate release (r95) has most of the issues fixed and is a good daily driver, also the facial recognition is all fixed and Magisk is working with no issues, I've been able to use my banking apps for over the counter purchases again, tested and all working. Here is the method that worked for me -
How to flash Renovate and not stuff up. Remove SIM card before starting (I got this from Krabman's posts so I was not going to tempt fate at this stage by leaving in my SIM card, this is just a playing safe method for now).
1. Install TWRP (I trust you all are okay with everything up to this part)
2. In TWRP, swipe right and go into menu.
3. Wipe / Format Data / Yes
4. Reboot into RECOVERY
5. Flash DM-Verity
6. Wipe / Factory reset (by swiping)
7. Flash Renovate - I chose to root with Magisk cause it works for my banking apps.
8. After flashing Renovate, allow it to boot into System.
9. Do your basic setup and then reboot.
10. Now insert SIM and continue to setup your phone, Ti and all that good stuff. Phone is now rooted and working, TWRP is all working and safe to use as normal. This is the part that I did Ti restore and flashed Viper4Android etc etc.
11. Happy days for now, until we work out exactly what the issues are.......
The only thing I did not do was to try and flash the XSA firmware (Australia Unbranded) with the S8 CSC firmware installer. Apparently another user used it and it worked for them on the Note 8, however I did not want to chance it for now. The only drawback is on Volte and WiFi calling is missing but that's not a deal breaker. I might research a bit more before I try to flash the CSCSelection_S7_S8 zip.
AndiF85 said:
I will give it a try once oem unlock returns. Hopefully this can be resolved soon. Being in jail sucks. I've tripped Knox so lost Samsung features and no root still so dont have root advantages.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
I was in the same boat as you - if Renovate floats your boat then check out my last post, I've installed Renovate and all working nicely again... Waiting for one week then in jail for another week sucked hard!
Great to hear it worked for you. I was thinking of using Renovate as well as it looks like the best option we have at the moment. Now you have confirmed it's all good I'll be doing it the day I'm released from OEM jail. When I flashed stock firmware I tried the note 8 xsa to see if it was any better than the Telstra version but instead just lost features and gained new things in settings which didn't even work so went back and flashed Telstra version.
I know it's wishful thinking but does Samsung pass work for you? I don't care for Samsung pay and health but Samsung pass was a nice feature.
Sent from my SM-N950F using Tapatalk
AndiF85 said:
Great to hear it worked for you. I was thinking of using Renovate as well as it looks like the best option we have at the moment. Now you have confirmed it's all good I'll be doing it the day I'm released from OEM jail. When I flashed stock firmware I tried the note 8 xsa to see if it was any better than the Telstra version but instead just lost features and gained new things in settings which didn't even work so went back and flashed Telstra version.
I know it's wishful thinking but does Samsung pass work for you? I don't care for Samsung pay and health but Samsung pass was a nice feature.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Just tested that out for you, unfortunately that is the only one that does not work (Well we know Samsung Pay won't work due to KNOX being tripped). It goes through all the setup okay, then on final authentication it says "Samsung Pass is temporarily unavailable, please try again later". So that's a bit of a bummer.. I've tested Android Pay, all good, and I also use NAB pay and works with no issues as well as long as you set it up correctly with Magisk (there is a bit of a method to follow but I found a way to make it work - in case your with NAB at all).
I might make a suggestion to mwilky to see if that could possibly be fixed in the ROM as I agree it's a great feature.
Edit - That question was already asked by another user, mwilky says that it does not work the moment TWRP is flashed and not likely able to be changed. Bummer.
Soft brick
How do you get out of the soft brick? I have the SM-N950F/DS but I do not know what REGION I need to download for the official firmware. Thanks for any help!
bwallis said:
How do you get out of the soft brick? I have the SM-N950F/DS but I do not know what REGION I need to download for the official firmware. Thanks for any help!
Click to expand...
Click to collapse
Use Samsung Smart Switch for that. it will tell you the region code for your phone. It could restore for you, or you could use http://fw.updato.com/, or SamFirm, to download appropriate ROM
Alright finally I'm out of jail.
About to download everything then going to attempt tonight.
Andsmith71 how have you found the rom over the past week?
Any issues?
still holding Root?
Does Bixby Voice still work?
Sent from my SM-N950F using Tapatalk
Hello all, i have searched endlessly on this site and didnt quite find my answer. Or didnt understand what to do, as i am not up to speed to what everything means. A little background...
i bought a used t713 not knowing it was "bricked?" (MDM/FRP). When i first powered it on i was unable to do anything as the home screen does not allow anything to be done. The message "Device turned off, contact IT" appears. Cant access settings nor turn it off.
In my desperate attemps to do a hard reset without being able to turn it off, i reset the tablet then pressed the combination of keys and got it to the "andriod recovery" screen. Tried to "wipe data/factory reset" but was not successful due to mdm. What makes my case unique is that i cant access anything such as setting so any youtube vids or other posts does not really help. Aside from the fact that i do not understand what anything means... Odin vs flashing vs rooting vs etc.
Can anyone provide a solution where a total newbie can follow the instructions?
Please see the attached photos for issues and tablet software version. ***once i figure out how***
So i cant figure out how to post the pics but below is the info from the "Android Recovery" screen
samsung/gts28vewifixx/gts28vewifi
7.0/NRD90M/T713XXU2BQD3
Also, i was able to ender the download mode, which i figured is Odin mode. From there i can see the following options:
FRP LOCK: ON
Secure Dowload: Enable.
with the info provided above what would be my first step?
Flash via odin? Then do a FRP bypass?
If you can enter Download Mode, then flash it with the latest of Android 6 and proceed to bypass FRP
This FRP lock is a joke because many can do it without any problem as long they read and do it properly
h
Beut said:
If you can enter Download Mode, then flash it with the latest of Android 6 and proceed to bypass FRP
This FRP lock is a joke because many can do it without any problem as long they read and do it properly
Click to expand...
Click to collapse
Is there any specific odin version to use? From reading there are a few places to get Android 6... sammobile?
The Odin version is not important as long as it’s close to the latest one. Search Google FRP bypass you will see many discussions from this forum. Read carefully what others did, you will see it’s a piece of cake.
You need to read In order to see mistakes others did too and why they failed.
I'm in the same situation. A used SM-T713 that has FRP lock on. I've researched the web and seen every YouTube scam there is. I've downloaded oldest firmware available on Sammobile and flashed with ODIN. I've also used the newest firmware available from Sammobile. Notta. I am so very very frustrated. There are about a bazillion people with this situation and I cannot find a one that has managed to bypass the FRP lock. If you know how to help, OMG, I would be sooooooooo very grateful. I'm not new to flashing. I have rooted many phones, flashed many ROMS, very familiar with TWRP and Superuser and Chainfires cfautoroot. Is there any hope? Of do I just smash the heck out of this thing and burn it to a puddle of plastic in the middle of my living room????
CanadaHugh said:
I'm in the same situation. A used SM-T713 that has FRP lock on. I've researched the web and seen every YouTube scam there is. I've downloaded oldest firmware available on Sammobile and flashed with ODIN.?
Click to expand...
Click to collapse
You should be patient , FRP is a joke as long as you know how. In order to bypass, you should be specific what build you currently have.
Forget the Android 7 because most methods which don't use OTG cable are not working. The best way is downgrade to Android 6.
I don't have this model but the most popular methods are using Talk Back to open chrome, Hot Spot to create new users, and using Assist to open chrome.
You see a lot of youtube videos which are not working because most posters don't understand a method only work with certain build and model.
As long as you can open Chrome to download needed apps , FRP will be gone . I can bypass FRP on 5 different Samsung tablets so it's not a rocket science as long as you know which method works and uses it.
This is an example of method using Talk Back
https://www.youtube.com/watch?v=fhP_egvc6v0
Thank you for taking time to reply. I've seen this exact message you pasted here. I've tried to do all 3 possibilities offered with no success. I have current os of nugat. I've got backup from sammobile. Also used Odin to attempt downgrade to 6...fail because ftp lock prevents flash in odin. Tried talk back. ..the L during tutorial is prevented. So, for me anyway, this is rocket science! Please allow me the dignity of being able to read, search, view, attempt. ...every conceivable avenue for solution.
My device is SM-T713 running latest update of Nougat with FRP lock on. I do not know the previous user name and password so can not bypass FRP. Does this explanation clarify my dilemma? Do you possibly have a blueprint of the rocket science? Most of the Web results lead to dead end spams.
I see a common mistake of failing to bypass FRP: using methods only work with Android 6. All methods I mentioned only work with Android 6, use it to bypass FRP a tablet with Nougat is pointless because it's not applicable.
Downgrade to Android 6, you need to flash 3 files BL, AP, and CSC. Common mistake when downgrade is just flashing the AP file only.
This is an example of failing to downgrade
https://forum.xda-developers.com/showpost.php?p=76148948&postcount=9
I have done downgraded Android 7 to Android 6 hundred times without any issue to bypass FRP.
Again, thank you for taking time to reply. I sincerely appreciate your efforts.
Sent from my SM-N900W8 using Tapatalk
As long as you can downgrade, I am sure you can bypass FRP as Android 6 has many security flaws that a certain method will work.
Like SM-T280 , it's Lollipop but I can only use Talk Back method with older build. SM-T670, SM-T377 also is Lollipop but I have to use Hot Spot method with the current build.
SM-T560, Hot Spot method only works with older builds of Android 6, the latest build of Android 6 has to use Assist method.
SM-T580, P580 I can bypass FRP on both Android 6 and 7, but the method used in Android 7 will trigger Knox count.
These are few examples what can be done to bypass FRP on 6 different Samsung tablets . It's the same like a certain move in self defense, you cannot use it in every single situation or position. Apply wrongly, you will be hit or fail. As long as you know which one will work, FRP lock is a joke to me.
Beut said:
As long as you can downgrade, I am sure you can bypass FRP as Android 6 has many security flaws that a certain method will work.
Like SM-T280 , it's Lollipop but I can only use Talk Back method with older build. SM-T670, SM-T377 also is Lollipop but I have to use Hot Spot method with the current build.
SM-T560, Hot Spot method only works with older builds of Android 6, the latest build of Android 6 has to use Assist method.
SM-T580, P580 I can bypass FRP on both Android 6 and 7, but the method used in Android 7 will trigger Knox count.
These are few examples what can be done to bypass FRP on 6 different Samsung tablets . It's the same like a certain move in self defense, you cannot use it in every single situation or position. Apply wrongly, you will be hit or fail. As long as you know which one will work, FRP lock is a joke to me.
Click to expand...
Click to collapse
Thank you for taking time to explain the joke
Seriously, this security lock is a joke as I can do with ease on different Samsung tablets. Read this forum you will see, newbies would have troubles to unlock their tablets
but eventually they are able to bypass this FRP lock. So again, it's not a rocket science, you need to be patient and try different methods.
I started the same like yours, didn't know what to do. However, by learning and practicing, I do actually see it's a piece of cake as long as you understand which method can apply to a certain build or OS.
Beut said:
I see a common mistake of failing to bypass FRP: using methods only work with Android 6. All methods I mentioned only work with Android 6, use it to bypass FRP a tablet with Nougat is pointless because it's not applicable.
Downgrade to Android 6, you need to flash 3 files BL, AP, and CSC. Common mistake when downgrade is just flashing the AP file only.
This is an example of failing to downgrade
https://forum.xda-developers.com/showpost.php?p=76148948&postcount=9
I have done downgraded Android 7 to Android 6 hundred times without any issue to bypass FRP.
Click to expand...
Click to collapse
So i downloaded odin, samsung drivers and 7zip. As well as APK6 firmware (latest Android 6 fw i found on updato). From the APK6 download, there was only one tar.md5 file. Question is should i find fw that has the 3 seperate files or running the one i have in AP should work?
Flash the AP file only, it may not erase user data and factory reset. You can try it, it may pass Odin but starts at the same lock screen again.
If you need the BL and CSC files, I could upload for you, but this is an US version.
Beut said:
Flash the AP file only, it may not erase user data and factory reset. You can try it, it may pass Odin but starts at the same lock screen again.
If you need the BL and CSC files, I could upload for you, but this is an US version.
Click to expand...
Click to collapse
So i was able to downgrade the firmware to APK6, with only the AP file but i was greeted with an "to start up device enter password" message. Something i havent seen before... not same lock screen
Tried to do factory reset and failed due to mdm.
https://drive.google.com/file/d/1pwDFqzrl3Dqt9V6ZpDCz60tOutmmpYOM/view?usp=sharing
Flash again with BL, AP, and CSC , this is US firmware.
Beut said:
https://drive.google.com/file/d/1pwDFqzrl3Dqt9V6ZpDCz60tOutmmpYOM/view?usp=sharing
Flash again with BL, AP, and CSC , this is US firmware.
Click to expand...
Click to collapse
Thanks for the files. Flashed all three files and was still greeted with the enter password screen. Mdm still prevents factory reset when trying to resetthru recovery menu. Any other pointers?
Gamma35 said:
Thanks for the files. Flashed all three files and was still greeted with the enter password screen. Mdm still prevents factory reset when trying to resetthru recovery menu. Any other pointers?
Click to expand...
Click to collapse
Are you on marshmallow now or nougat?
ashyx said:
Are you on marshmallow now or nougat?
Click to expand...
Click to collapse
I am on marshmallow.
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.
jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers
stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/
jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.
Hi all. Succesfully rooted my S8 Tab Ultra and was running fine for the past week.
Just rebooted the tablet and its showing "Custom Binary(boot) Blocked due to remaining installment balance" I've read around the forum and apparently its for people who haven't paid for the device fully which I have, paid in full on pre order.
The only way it seems to get it to boot is to flash the original firmware my model is SM-X900NZAFXAR and I can't find the firmware does anyone know how I can get the tablet to boot?
Tried Samsung support but they didn't help
Hello! Get SamFirm at https://samfirmtool.com/ (v0.5.0 is the latest), for model put SM-X900, for Region put XAR. I haven't received mine yet (not until the middle of next month), but this is the closest I could find to what should be the correct firmware. Click "Check Update", then click "Download". It's been too long for me away from Samsung - I don't remember if it matters if you let it decrypt automatically or not. The answer should become apparent, though. At worst, you'll just have to redownload the firmware with the option to decrypt unchecked in SamFIrm.
You can check your CSC (Region) by (copying/pasting someone else's instructions):
go to settings - about - software information - service provider SW ver. The region code (CSC) will be written there.
I don't know if your CSC will match XAR. I don't find anything for XAA or XAS yet in SamFirm.
Good luck! This is concerning since I had planned on rooting mine.
Thanks for the reply. I've downloaded the XAR firmware but now I have another problem getting the USB device not recognised. Device descriptor request failed. Tried locking the bootloader again now its stuck with a Hash fail on boot and wont turn off. Can't unlock the bootloader again. 99% sure its not the laptops fault its the one i rooted on but will try another pc tomorrow. Will have to try Samsung again as although I have rooted which voids warrenty its there mistake on my device thinking it has finance outstanding that has caused the failure.
Cheers
Jono0907 said:
Thanks for the reply. I've downloaded the XAR firmware but now I have another problem getting the USB device not recognised. Device descriptor request failed. Tried locking the bootloader again now its stuck with a Hash fail on boot and wont turn off. Can't unlock the bootloader again. 99% sure its not the laptops fault its the one i rooted on but will try another pc tomorrow. Will have to try Samsung again as although I have rooted which voids warrenty its there mistake on my device thinking it has finance outstanding that has caused the failure.
Cheers
Click to expand...
Click to collapse
You got the latest Samsung drivers installed, as linked to in the SamFirm\Samsung Driver subfolder? (link leads to https://samsungusbdriver.com/category/download)
Wait... Is OEM Unlock still enabled in Dev Options? It might be salvageable even though you have locked the bootloader...
Thank you edor for the help the tablet is running again now however it is unrooted now and the OEM unlock option is missing. The USB fault was resloved using a different PC not sure whats going on with my laptop.
Once in download mode i was able to download the XAR version of the Tab S8 Ultra fimrware from SamFirm and reflash with Odin which brought it back.
I'm not sure if running XAR csc will cause problems? I am in the UK I think my csc originally was OXM which is the universal one but cant find an OXM version at the moment.
fkofilee I actually locked the bootloader from the download mode menu which i shouldnt have. I don't have the option now so think I need to wait for the OEM unlock to show in settings.
For anyone else who has the "Custom Binary(boot) Blocked due to remaining installment balance" Need to reflash back to original firmware to boot and apparently it will re-check in 7 days so cannot be rooted in that time.
I have an open ticket with Samsung to try and find out why my tablet thinks it has finance. The confirmed on the phone that it was paid in full.
I wonder if the S7 Bootloader that i rooted had anything to do with it. Will retry with the bootloader when i can and report back.
@Jono0907 I'm glad you got it back working. I apologize if the XAR firmware has anything to do with your OEM unlocking not being available. Thank you for the advice for myself and for others to follow if we encounter the same problem. You had used the S7 bootloader? I would expect that to be the problem but as I said, I'm rusty on Samsung, and totally unexperienced in Samsung tablets - I only know what I've read in this section so far.
My tablet is working because of your advise so I'm happy. Found the EUX firmware which feels like it should be what my tablet should be running so will flash that and see if Unlock comes back. Tried all the tricks with date/time to try and trick it but no luck.
Also was going to add my experience with Samsung support. He agreed that if the tablet was wrongly reporting it was in finance then it wouldn't have been my fault but also said Samsung would not help because I had rooted the device. He didnt talk about reflashing firmware just said that I needed to send it to them for a new motherboard to repair Knox at a cost of at least $400(£300)
I planned to root s8 ultra, now afraid. So, is it safe to root it, and can someone put here whole procedure?
Many thanks
It's pretty much always safe because you can go back to "Download Mode" and reflash the original firmware.
It will however trip Knox which is Samsungs securityh (Done by breaking a physical fuse on the motherboard) which cannot be undone. This voids the warrenty and could cause problems with Google Pay and other things.
The basic process for rooting the S8 is
1. The process requires OEM Unlocking which some carriers in USA seem to be blocking. If you can OEM unlock it will be an option within the developers options in settings. Sometimes it doesn't show up right away.
2. Download SamFirm and get the firmware for your device. The Model for the Non-5G Tab S8 is SM-X900 and put in the CSC code for your region. Samsung simplified CSC codes before the release of the Tab S8 so you can see the list on wikipedia when searching for the tablet it is probably better to look up how to check your CSC code on your tablet to make sure you are getting the right one.
3. Install Magisk Manager on your tablet. Extract the firmware and copy the AP file to your tablet. Open Magisk Manager and point it at the AP file that you copied. Once complete it should give you a Magisk Patched file copy it back to your computer.
4. Install Odin and Samsung USB drivers. In Odin Select the Magisk Patched file for AP then add the BL file that you downloaded from SamFirm and the CSC file. (This will factory reset the tablet). You can leave CP and Userdata blank.
5. Reboot the tablet into Download Mode. This can be done by powering it off connecting it the the PC and when you see the charge symbol hold down Volume up and Volume down till you get to the Download Mode Menu. From here you need to press the option for OEM Unlock and then go to the download screen. Now press start in Odin.
That's pretty much it
ivanox1972 said:
I planned to root s8 ultra, now afraid. So, is it safe to root it, and can someone put here whole procedure?
Many thanks
Click to expand...
Click to collapse
I want clearly explanation, I don't know about this.
Jono0907 said:
It's pretty much always safe because you can go back to "Download Mode" and reflash the original firmware.
It will however trip Knox which is Samsungs securityh (Done by breaking a physical fuse on the motherboard) which cannot be undone. This voids the warrenty and could cause problems with Google Pay and other things.
The basic process for rooting the S8 is
1. The process requires OEM Unlocking which some carriers in USA seem to be blocking. If you can OEM unlock it will be an option within the developers options in settings. Sometimes it doesn't show up right away.
2. Download SamFirm and get the firmware for your device. The Model for the Non-5G Tab S8 is SM-X900 and put in the CSC code for your region. Samsung simplified CSC codes before the release of the Tab S8 so you can see the list on wikipedia when searching for the tablet it is probably better to look up how to check your CSC code on your tablet to make sure you are getting the right one.
3. Install Magisk Manager on your tablet. Extract the firmware and copy the AP file to your tablet. Open Magisk Manager and point it at the AP file that you copied. Once complete it should give you a Magisk Patched file copy it back to your computer.
4. Install Odin and Samsung USB drivers. In Odin Select the Magisk Patched file for AP then add the BL file that you downloaded from SamFirm and the CSC file. (This will factory reset the tablet). You can leave CP and Userdata blank.
5. Reboot the tablet into Download Mode. This can be done by powering it off connecting it the the PC and when you see the charge symbol hold down Volume up and Volume down till you get to the Download Mode Menu. From here you need to press the option for OEM Unlock and then go to the download screen. Now press start in Odin.
That's pretty much it
Click to expand...
Click to collapse
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
emko7 said:
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
Click to expand...
Click to collapse
Sorry mate never done the HOME CSC flash I've always been happy to wipe the device hopefully someone here knows?
emko7 said:
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
Click to expand...
Click to collapse
Uh-oh. I was just getting ready to update to the latest firmware, Maybe I'll have to wait, see how this plays out.
lloydsw said:
Uh-oh. I was just getting ready to update to the latest firmware, Maybe I'll have to wait, see how this plays out.
Click to expand...
Click to collapse
For what it's worth on my S8 Ultra, I updated from rooted April update to rooted May's update perfectly fine without wiping data. Always do backups, though, things happen.
roirraW edor ehT said:
For what it's worth on my S8 Ultra, I updated from rooted April update to rooted May's update perfectly fine without wiping data. Always do backups, though, things happen.
Click to expand...
Click to collapse
Yup, worked fine on my S8. Sigh of relief!
I don't know if I was supposed toflash STOCK ROM for Germany-DBT or Germany-T-Mobile. So I flashed the first. Forgot to check if there is 'OEM unlocking option', and flashed magisk-patchet boot.img. At first, root worked, however nex morning on booting, on samsung logo was written 'only official released binaries are allowed'.
So, I flashed again the same rom, now there is no 'OEM unlocking' opt in dev ops. Tutorials on unlocking it don't work.
Can you suggest something ?
I'm thinking to go Germany(T-Mobile) stock rom, don't know if I should. Don't know if it will make hard-brick if rom is not for this Note 8.
Should I try it ?
However, mate, I'll be grateful if you know what should I do and suggest something, cuz I'm starting to feel like fighting Diablo without a weapon.
Thanks
EDIT: Found a way to get OEM UNLOCKING (with automatic updates try).
What's you're model number
Dr.Lost said:
What's you're model number
Click to expand...
Click to collapse
Well I fixed it, I just went auto-update; after it started downloading , I stopped it & OEM unlocking appeared.