Galaxy s9 + Parental Control --> normal boot sequence broken : Custom binary blocked by OEM Lock.
.
.
@joelp wrote:
After the update and the first reboot, the phone worked fine. Then I tried parental control. Until then OK, but then I turned it off, launcher was about to restart (looks like). After rebooting my phone says error:
Custom binary blocked by OEM Lock.
I tried twice. Each time it was necessary to flash the Samsung ROM, disable OEM lock and then flash /e/OS back
.
@muww wrote :
When I try to get into Recovery Mode via the buttons it states “Custom binary blocked by OEM lock”
When I try to get into Bottloader Mode via the buttons it states “Custom binary blocked by OEM lock”
I can get via the buttons into Download Mode (Odin Mode). There it states “FRP lock: Off OEM lock: On”
So in my opinion the only Mode that works is Odin Mode.
I invested some hours today and came to the only conclusion: Maybe there is a possibility to flash the stock ROM (Standard Android) without wiping the current e/OS, resetting the OEM lock in the Standard Android and having the possibility to change the boot priority to e/OS again via TWRP.
Are there any ideas out there?
I can imagine that this problem could occur in many cases by trying out the new parental control feature (big thanks for implementing anyway!)
.
2024-08-15 by piero
For the moment, i see two possible workarounds,
- the first one we tried today is to restore Official SamsungOS without wiping or formating the /data partition (using HOME_CSC firmware variant). The goal is to gain access to the content of the internal storage (/data/sdcard) folder to save or backup it (photos prior to average users).
- the second one (not yet engaged) is to simply flash TWRP, but it is not possible on devices where the bootloader was relocked
- a mix of both (not yet engaged) is to insert TWRP renamed recovery.img into a Samsung firmware (HOME_CSC version) to gain the possibility of a full access to the /data partition (not sure it will works because of possible OEM protection --> .MD5 extension may missing when repacking the AP firmware part) If it work, from this state (SamsungOS+TWRP) we may be abble to reinstall /e/, without wiping or format /data .
.