Hi,
Samsung Galaxy J5 (2016) - SM-J510FN/DS
I have flashed the TWRP recovery (3.0.2) and then installed SU Root.
As I wanted to turn on "System UI Tuner" but it did not work, I turned off the "developer options" in the settings.
After restart my mobile is now in "Custom binary blocked by frp" [secure fail:kernel].
How can I solve that?
Winf2005 said:
Hi,
Samsung Galaxy J5 (2016) - SM-J510FN/DS
I have flashed the TWRP recovery (3.0.2) and then installed SU Root.
As I wanted to turn on "System UI Tuner" but it did not work, I turned off the "developer options" in the settings.
After restart my mobile is now in "Custom binary blocked by frp" [secure fail:kernel].
How can I solve that?
Click to expand...
Click to collapse
Please reflash the stock firmware. Alternatively I have read that flashing only the boot.img file ahould do the trick without erasing data but I can't really confirm this.
FRP lock is caused by the bootloader detecting that a change was made. To disable security detection you need to keep enabled OEM Unlock in Dev Settings. It gets deactivated always when you turn off dev options.
BTW Samsung removed the System UI tuner from Marshmallow so your best bet for that is an XPOSED module or a custom ROM based on android AOSP, roms that don't have that disabled. Samsung is stupid
Thank you!
The stock firmware was ~1.4GB. After flashing root has gone, but almost all configuration was still there. Either it was not overwritten or the backup of Samsung did the job...
Winf2005 said:
Thank you!
The stock firmware was ~1.4GB. After flashing root has gone, but almost all configuration was still there. Either it was not overwritten or the backup of Samsung did the job...
Click to expand...
Click to collapse
Oh well it did factory reset, right? Also the backup feature is mostly Gogle's that's how I manage to keep most of my information even tho I'm trying new ROMs every month.
The cool thing was, that the installed APPs have all been there. So yes, google maybe did a big part, but I think this was no complete factory reset. I did it completely after the official advice of Samsung's homepage.
When activating the oem unlock you can install Twrp, kernel or custom rom without the activation of FRP security that is activated when you establish a security pattern in the device
When the binary is blocked by the FRP you must install the factory firmware, then enter the recovery and do a factory reset since the FRP prevents external access to the system and data as prevention
You will be prompted for the email and password of the previously used account
Thanks a lot
Amarius1 said:
Please reflash the stock firmware. Alternatively I have read that flashing only the boot.img file ahould do the trick without erasing data but I can't really confirm this.
FRP lock is caused by the bootloader detecting that a change was made. To disable security detection you need to keep enabled OEM Unlock in Dev Settings. It gets deactivated always when you turn off dev options.
BTW Samsung removed the System UI tuner from Marshmallow so your best bet for that is an XPOSED module or a custom ROM based on android AOSP, roms that don't have that disabled. Samsung is stupid
Click to expand...
Click to collapse
I have saved my data on Galaxy J5 2016. You advice to reflash only original "boot.img" is excelent cure.
Related
So, i'm using a SM-N900 and i have flashed a custom boot image (along with rooting). The issue arises when I try to encrypt the phone, and it never works. I found that logcat prints out this message when it attempts to encrypt.
======================
The kernel binary has been changed.
The platform/kernel binaries should be synchronized for running Secure Storage.
Please use the same version of platform/kernel binaries.
======================
Click to expand...
Click to collapse
I'm wondering if there's some sort of security feature I can disable to allow my custom boot image to be encrypted, or if i just have to flash it a different way.
Thanks in advance
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
not work
says: SECURE CHECK FAIL : (BOOTLOADER)
also for me....not work....
Gracias !
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Hi Sir,
Also just went through with that dreaded 'Only official released binaries are allowed to be flashed' while trying to install TWRP 3.2.1-0 and root via magisk v16. My G950FD was just a few days old though bought this in used condition. Its currently on v8 Oreo. After flashing this with the stock rom https://forum.xda-developers.com/galaxy-s8/development/rom-galaxy-s8-t3749171 the phone sprang back to life its the 2nd day and still OEM unlock option has not showed up and am quite impatient already wanting to have TWRP and root. After flashing your Nougat bootloader, will I follow this same procedure again? https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
Thanks
So what to do, i wait seven days on my S8. OEM unlock appears, but the phone stays in prenormal mode?
Worked perfectly for me and I also have a G950FD. Thanks a lot man !!!
Wow thanks a lot! This worked great, I was about 3 days into the wait after I made a mistake when flashing..
Really wanted Notorious kernel so I can use Dex, all solved now.
THanks!
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Thank you! I have been fighting with this for what seems like forever and thought I was screwed but this helped! :good:
se puede usar ese metodo para s8+ con oreo ?
I got same problem 'Only official released binaries are allowed to be flashed' and i tried to flash stock rom but it gives fail. Also it says sw rev check fail 2 binary 1 on download mod. how ca i solve this?
The10y said:
I got same problem 'Only official released binaries are allowed to be flashed' and i tried to flash stock rom but it gives fail. Also it says sw rev check fail 2 binary 1 on download mod. how ca i solve this?
Click to expand...
Click to collapse
Just odwnload one firmware bit 2
maurote said:
Just odwnload one firmware bit 2
Click to expand...
Click to collapse
Could you please elaborate? I don't understand. I'm having the same issue.
Try this:
1)- change phone date manually back 8 days
2) go to software update and check for update. You should receive errors messages sometime. Don't worry. Just ignore it.
3)- restart phone immediately after checking software update and go to Developer Options and you should see OEM Unlock appear back. You may need to try checking software update few times to get it work.
Additional information:
https://forum.xda-developers.com/showpost.php?p=76746640&postcount=12
help please I had the same problem, try flashing the attached boot manager but I get error in odin
please twrp for CRGB not work
doesn't work, fail in both normal odin n the special odin.
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
Hello,
Could you please tell us if that gonna work for S8 G950FD Oreo 8.0.0 AUG 2018 G950FXXU3CRGH?
I used RMM-State_Bypass_Mesa which is set vaultkeeper.feature parameter to 0 and remove /system/priv-app/Rlc" and maybe more!!
Because it's song good until the test reboot where the system is still stucked with this message.
Many thanks
arcanemyth said:
Hi everyone,
I got a new S8 G950FD (android for that matter) and updated it to Oreo right out of box. Rooted with TWRP and Magisk 16.0.
Got the dreaded 'Only official released binaries are allowed to be flashed' message after rebooting and couldn't help but flash stock firmware and wipe all the data. Fortunately I still had not wiped the older phone and had all the data.
Here's what you can do to avoid a 7-day wait for OEM unlock option to appear.
Download the attached bootloader from Nougat G950FXXU1AQL5 and flash it via Odin (PrinceComsy version). It should let you keep TWRP and your phone data intact while also removing the RMM Prenormal flag.
OEM Unlock option won't appear in Developer Options, but you don't need it as far as FRM and OEM Unlock are both OFF in Download mode.
Let me know your results and comments.
Click to expand...
Click to collapse
I just get "SECURE CHECK FAIL : (BOOTLOADER)"
milaniov said:
I just get "SECURE CHECK FAIL : (BOOTLOADER)"
Click to expand...
Click to collapse
At a guess without more info I would say you are trying to downgrade your firmware
Yesterday, I updated my S8+ to the Pie Beta and tried to flash a TWRP .tar file using Odin but I'm met with an error reading, "Only official released binaries are allowed to be flashed." I then rebooted, checked Developer Options, and saw that OEM Unlock is enabled. Does anyone know the reason why this is happening and maybe how to remedy the issue? Maybe the BL is on more secure or unsupported version?
Soapy! said:
Yesterday, I updated my S8+ to the Pie Beta and tried to flash a TWRP .tar file using Odin but I'm met with an error reading, "Only official released binaries are allowed to be flashed." I then rebooted, checked Developer Options, and saw that OEM Unlock is enabled. Does anyone know the reason why this is happening and maybe how to remedy the issue? Maybe the BL is on more secure or unsupported version?
Click to expand...
Click to collapse
Have a look through this thread
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
spawnlives said:
Have a look through this thread
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Click to expand...
Click to collapse
Thanks a lot for the link, the OP and your solid answers gave me an idea.
Issues when trying to apply the solution while on ZSA5:
OEM Unlock option was on and visible by default. DL mode wouldn't display OEM, FRP, or RMM statuses.
Solution:
I decided to downgrade to Oreo and tried the OEM Unlock calendar trick as it wasn't visible by default this time. Afterwards, I rebooted into DL mode and this time it displayed the OEM, FRP, and RMM statuses. I then flashed TWRP succesfully and decided to flash a custom stock ROM based on Pie via TWRP instead.
Also done a "small" guide how to get this
https://forum.xda-developers.com/galaxy-s8/how-to/how-to-bypass-rmm-prenormal-to-install-t3891193
Okay, so I flashed TWRP onto my Galaxy S8 using Odin and then it said my workspace has been locked due to unauthorised software being installed on the device, so I then went and found my firmware online to flash it onto my device, hoping to bypass my workspace restriction but then found flashing the software factory reset my device, so I lost TWRP recovery. How on Earth do I flash TWRP onto my Samsung Galaxy S8 without being blocked from using my device? I’m a noob at this stuff but have some know how to get this far... Any help would be greatly appreciated! Thanks.. My end goal is to root my phone with Magisk and bypass SecurityNet restrictions on my phone from unlocking my bootloader.
Kriranda said:
Okay, so I flashed TWRP onto my Galaxy S8 using Odin and then it said my workspace has been locked due to unauthorised software being installed on the device, so I then went and found my firmware online to flash it onto my device, hoping to bypass my workspace restriction but then found flashing the software factory reset my device, so I lost TWRP recovery. How on Earth do I flash TWRP onto my Samsung Galaxy S8 without being blocked from using my device? I’m a noob at this stuff but have some know how to get this far... Any help would be greatly appreciated! Thanks.. My end goal is to root my phone with Magisk and bypass SecurityNet restrictions on my phone from unlocking my bootloader.
Click to expand...
Click to collapse
Follow this to the letter and you'll have twrp running. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
PS...go to page one first post
xlucian said:
Follow this to the letter and you'll have twrp running. https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
PS...go to page one first post
Click to expand...
Click to collapse
hi.
i have an g950fd on 8.0
with this new firmware... 8.0 G950FXXU4CRKB
when i install "twrp", "RMM-State_Bypass_Mesa" and "magisk 18"
then it boot ok. BUT, when reboot.. BAM!
soft brick with the message "only official released binaries are allowed", even twrp i cant access...
ive gotten on download and flashed the firmware again and its on; but i really want my root....
so my rmm didnt worked.. how can i bypass this?!?!
anyone has a new rmm? please!!
b4 k3 s3
what i think is that i get oem unlock --> twrp-3.2.3-2-dreamlte --> rmm + magisk + samsung-antiroot-removal-2.4
and at some point the firmware reblock oem
what can i do? thanks!
Are you using the dm-verity thing?
rodrigodornas said:
hi.
i have an g950fd on 8.0
with this new firmware... 8.0 G950FXXU4CRKB
when i install "twrp", "RMM-State_Bypass_Mesa" and "magisk 18"
then it boot ok. BUT, when reboot.. BAM!
soft brick with the message "only official released binaries are allowed", even twrp i cant access...
ive gotten on download and flashed the firmware again and its on; but i really want my root....
so my rmm didnt worked.. how can i bypass this?!?!
anyone has a new rmm? please!!
b4 k3 s3
what i think is that i get oem unlock --> twrp-3.2.3-2-dreamlte --> rmm + magisk + samsung-antiroot-removal-2.4
and at some point the firmware reblock oem
what can i do? thanks!
Click to expand...
Click to collapse
at step 7 from install twrp...
when you are in twrp chose format and format the data to remove encryption.
I also got the message "only official released binaries are allowed" and twrp was gone and replaced by factory recovery
xlucian said:
at step 7 from install twrp...
when you are in twrp chose format and format the data to remove encryption.
I also got the message "only official released binaries are allowed" and twrp was gone and replaced by factory recovery
Click to expand...
Click to collapse
dude same here!
i dont even can enter on recovery even twrp or samsung..
and i formated too...
so..... its a new block? im using the worng rmm?
im on b4 k3 s3
i can downgrade to any b4 is that correct?
any b4 with root related?
thanks!
rodrigodornas said:
dude same here!
i dont even can enter on recovery even twrp or samsung..
and i formated too...
so..... its a new block? im using the worng rmm?
im on b4 k3 s3
i can downgrade to any b4 is that correct?
any b4 with root related?
thanks!
Click to expand...
Click to collapse
try and start from scratch
find the latest oreo firmware for you
flash it with odin and make sure OEM unlock is enabled
then follow again the guide...make sure you format data after step 7
xlucian said:
try and start from scratch
find the latest oreo firmware for you
flash it with odin and make sure OEM unlock is enabled
then follow again the guide...make sure you format data after step 7
Click to expand...
Click to collapse
i did...
today i enter on "oneclickroot" to check if its another way so i can root my device and the site says:
"SORRY
There Is No Root At This Time
Brand: samsung
Model: sm-g950f
Android Version: 8.0.0 (r16nw.g950fxxs4crlb)"
i found that the first firmware from b4 "G950FXXU4CRI5" on onclickroot appear rootable!
the same bootloader permit me to downgrade? or have other issues?
if oem unlock i just flash with odin?
thaks
rodrigodornas said:
i did...
today i enter on "oneclickroot" to check if its another way so i can root my device and the site says:
"SORRY
There Is No Root At This Time
Brand: samsung
Model: sm-g950f
Android Version: 8.0.0 (r16nw.g950fxxs4crlb)"
i found that the first firmware from b4 "G950FXXU4CRI5" on onclickroot appear rootable!
the same bootloader permit me to downgrade? or have other issues?
if oem unlock i just flash with odin?
thaks
Click to expand...
Click to collapse
You can flash with odin original firmware even if you don't have oem unlock.
But, to install twrp and root you NEED to have the oem unlock enabled in the developer settings
xlucian said:
You can flash with odin original firmware even if you don't have oem unlock.
But, to install twrp and root you NEED to have the oem unlock enabled in the developer settings
Click to expand...
Click to collapse
but about downgrade.. what is my barrieir?
can just downgrade to same bootloader or i can downgrade to others versions?
thanks!!
i flashed stock room on my s8, do i need to wait 7 days again to flash twrp? oem lock is off
trexander said:
i flashed stock room on my s8, do i need to wait 7 days again to flash twrp? oem lock is off
Click to expand...
Click to collapse
Depends, will have to check in download mode, if kg state and/or rmm state is prenormal then you will have to wait.
Om my s8 if i flash firmware i can modify my phone as soon as i connect to the imternet.
deleted
i have J730F and will going to flash twrp soon on it and what i experienced that we need Odin , custom recovery file, turning on development tool by tapping 7 times the build number then turning on OEM unlock then flashing recovery, but better to uncheck auto reboot on odin to get the recovery flash properly.
now u said u have J730GM and no idea this devices belong to which country and sim lock ?
will be sharing my result after getting succeed on my device of flashing recovery
deleted
nomadicdev said:
if you have oreo, your rom will lock you out after flashing twrp, and you'll have to wipe it all and wait a week to unlock owm unlock again. gm is singapore/thailand/ india I think. of course no sim lock, I think that's just a US thing
There's a specific method to flash twrp, and I assume one has to format and reflash the rom from within twrp after decryption
Click to expand...
Click to collapse
OH ic
well yes i have oreo and i was going to start the procedure of flashing custom recovery, my model is J7 Pro not (2017) but they both are same, now not sure what will happen after flashing custom recovery but hopping the things will go smoothly,
any thanks dear for the information
i have successfully flashed twrp the latest one on my J7 Pro with also flashing RMM-State_Bypass_Mesa_v2 and no-verity-opt-encrypt-6.0 then booted up into stock oreo rom and found my oem lock in developer options is there and my device is working absolutely fine so far
now going to flash the S9 One ui rom on it
Thank U