In developer options, toggle the “Allow OEM unlocking” setting
Reboot into download mode following the instructions below
Once into download, long press the volume up button and follow the instructions on the screen
After the bootloader is unlocked, your data will be erased, so make sure to back it up first.
Now, once the system has finished booting, you MUST connect to a WiFi network, enable developer options again, and make sure that the OEM unlocking toggle is on and greyed out. If you do not see the toggle on the developer settings, close the settings and try again a few times.
At this point and before I would guess the device should be online. The blocked custom binaries message indicates the device is prenormal … that must be released online.
Notice also the two cycles of Download mode before you send Recovery.
I am really drawing attention to the fact that the device has not done what is required. (Imagine that Samsung has complex locks; they will only open in the event you follow the guide very accurately.)
Have you had the device online? This is required in order to connect with Samsung servers.
Put another way, I draw attention to “Step2” (send recovery) was attempted before “Step1” (nothing happens with the volume button up) is complete.
reboot to normal mode and disallow “OEM unlocking”
apply a factory-reset from settings.
connect to the internet for a few minutes to disable prenormal state
then allow “OEM unlocking”
and reboot to download mode to press the volume up button
here /e/ instructions says :
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
hold Volume Down + Volume Up and connect the USB cable to PC.
Now, click the button that the onscreen instructions correlate to “Continue” and/or “Unlock Bootloader”.
I am sorry. It is an error in my writing. Actually I did reboot in fastboot mode and lauched your commands.
it has to be done immediatly
I am trying but without any effect. Executing “adb reboot download”. Then immedialty at restart, I let volume button up pressed before the screen is displayed. Or another time just after the screen is displayed. No effect.
Your step ot step procedure worked. But it didn’t work via “adb reboot download”. Only the second try where I used the “3 button pressed” from tab off in order to acceed the download mode. Previously I had always used the “adb reboot download” . I don’t know if it is the cause. Here is what was displayed:
ok, was not sure, so i choosed lazy / fastest,
my bad…
reboot to normal mode with volume down + side key as indicated to restart the phone.
it should do the unlock and factory reset.
then
After the bootloader is unlocked, your data will be erased, so make sure to back it up first.
Now, once the system has finished booting, you MUST connect to a WiFi network, enable developer options again, and make sure that the OEM unlocking toggle is on and greyed out. If you do not see the toggle on the developer settings, close the settings and try again a few times.
I am sorry. I redid the procedure and in fact after the first “button volume up”, Id did another smart instead of the indicated long press. Pfff … I am dumb. Too many informations. Really sorry
Now I have this screen:
yes multiples guides references can often leads to confusion..
when you will be ready to flash recovery, be aware that Odin4 don’t have any “no-reboot” option,
so prepare your fingers to reboot immediatly into recovery mode, or use Heimdal..
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
hold Volume Down + Volume Up and connect the USB cable to PC.
Now, click the button that the onscreen instructions correlate to “Continue” and/or “Unlock Bootloader”
I always rebooted in dowload mode with adb reboot download. Which is not equivalent. And I believed that that I had to press long volume up once in that download mode.
I am so dumb. I lost time and fortunately you could help.
Merci !!!
so the Heimdall v2.2.2 i builded on my Ubuntu will not be usefull as it was recently reported as non working on an other system.
if Odin4 won’t works for rebooting immediatly, try using your Heimdall v1.4.2, but if it don’t works for your “recent” device,
i can help building Heimdall v2.2.2 for your mageia it is quite simple.
) and it is ok. The tab rebooted and I have now a message at startup that it is unlocked.