Hi there,
Since I can not get pass thru "Custom binary (Recovery) blocked due to remaining installemnt balance" error while flashing TWRP I would like to ask, hot wo relock my bootloader...
KG STATEL Normal
FRP Lock: off
OEM Lock off
Varanty void: 0
latest Android 10 update...
I was waiting like 10 days OEM Unclock option didn't come....
any help?
Related
good day!
i want to lock back my bootloader but everytime i do the fastboot oem lock or fastboot oem relock
always got this message "failed remote: command not allowed
failed remote: check password failed.
should i need my oem key from the time that i unlock my bootloader to relock again?
im running oreo latest update
thank you
loyyol said:
good day!
i want to lock back my bootloader but everytime i do the fastboot oem lock or fastboot oem relock
always got this message "failed remote: command not allowed
failed remote: check password failed.
should i need my oem key from the time that i unlock my bootloader to relock again?
im running oreo latest update
thank you
Click to expand...
Click to collapse
Yes. You will need the bootloader unlock key to relock the bootloader.
fastboot oem relock <bootloader key>
So I got my FRP unlock code from a service center on call (I don't have one in my city). But when I type:
fastboot oem frp-unlock *password*
It still shows FRP Lock upon reboot.
Please help, I flashed a Treble system image which didn't boot and somehow corrupted my TWRP recovery; I tried locking the bootloader and trying dload method, but now I'm stuck with a locked bootloader and locked FRP; dload doesn't work, eRecovery WiFi recovery doesn't work.
Again, I've got my FRP unlock code and after fastboot oem frp-unlock *password* , it shows:
...
<bootloader> The device will reboot and do factory reset...
OKAY [ 3.221s ]
finished. total time: 3.221s
It reboots, still FRP lock shown in fastboot
good friends after an update my google pixel stays in boot loop I have tried several ways to unlock the bootloader to install a stock rom from flashboot but every time i try to unlock the bootloader it tells me that i have to activate or unlock the oem option
I tried to do it with the adb flashtool but it gives me error
c:\adb>fastboot oem unlock
FAILED <remote: oem unlock is not allowed>
finished. total time: 0.044s
c:\adb>
I can not enter the Android system either from my Google Pixel since it is damaged the same to activate the option of OEM
I need someone to help me with this problem because the phone does not let me do anything for the fastboot because the bootloader and the OEM are blocked
Hi, I need some help with unlocking the bootloader of my phone [Huawei Y5 (DRA-LX3)] Please!
So, I am using the adb7fastboot method to unlock the bootloader, there are very limited options to do this process, but I've managed to find what might be the unlocker code for the command:
Code:
fastboot oem unlock xxxxxxxxxx (the unlock code)
Naturally, the warning screen appears on my phone (the one that tells you about erasing all of the data by unlocking the phone), and when I select "Yes" the phone displays an error:
unlock failed... return to fastboot in 3s
And the adb/fastboot window goes something like this:
Code:
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7
)
finished. total time: 6.137s
What do you think? Is there a solution that can save my life? Thanks by the way!
Hello everybody,
Today I tried to flash the following firmware with Odin. As in the instructions, I first flashed step 1 and then step 2 using Odin.
SM-A520FXXS8CSh5_8.1_REMOVE LOCK SCREEN WITHOUT LOSE user DATA WITH FRP ON bootloader ON
when booting I got the message:
Code:
NAD: PASSED
RPMB PROVISIONED
then i have flashed Step 1 and Step 2 with the following Image:
firmware.gsm-social
A520FXXS7CSAB_8.0_REMOVE LOCK SCREEN WITHOUT LOSE DATA WITH FRP ON OEM ON
Code:
FRP LOCK: ON
RP SWAEV: B: -1 K:8 S:8
sw rev. check fail(bootloader) device: -1, binary: 8
after that the phone did not start anymore. It can only be booted in download mode. I can no longer flash firmware because the binary version does not fit. I know that I need the right binary version, but of course there is no version -1. Is there a way to get the phone working again without losing the data.
many thanks for your help