Had anyone tried it before?
After I unlock my bootloader using the official method, it is a silly way to unlock your Arc S bootloader. You will lost your DRM key and FOTA bricked, I learned my lesson. If you want to unlock your phone Testpointer method is obviously a better way.
So I relock my bootloader again using a common method you can find online:
http://forum.xda-developers.com/show...php?p=20422618
fastboot flash -i 0x0fce getvar version
fastboot flash -i 0x0fce oem unlock 0xKEY
Error: cannot load '0x0fce' is what I got after execute these command.
I am so desperate to get my bootloader unlock again and manage to switch between locked and unlock state.
Is there something to do with preset.ta file so I can unlock my device again. If the re-lock patch involving this file.
Well! It seem to solved.
Using following command:
fastboot getvar version
fastboot oem unlock 0xKEY
Thanks you guys!
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
I'm trying to unlock lenovo z2 plus bootloader using adb and fastboot on fedora. I'm using platform tools version 29. I'm trying
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
but this command won't work. I get this error message
fastboot: invalid option -- 'i'.
Apparently fastboot --help also doesn't shows -i as an argument.
So how can I unlock the bootloader?
Ignore that i part,
Just use fastboot flash unlock unlcok_bootloader.img
According to my experience, under Qualcomm's EDL mode (9008), it can actually flash TWRP without unlocking the bootloader.
"fastboot oem reboot-edl" or "adb reboot edl" will reboot the phone into 9008 mode. You may try special EDL USB cable as well, especially under tricky situations.
You need to download (and install) qpst 2.7.474 and stock ROM (for prog_emmc_firehose_8996_ddr.elf). QFIL has a nice partition manager feature, which allows you to flash anything you want - of course, this will introduce risk of data loss/bricking etc, if improperly operated.
fun_jack said:
I'm trying to unlock lenovo z2 plus bootloader using adb and fastboot on fedora. I'm using platform tools version 29. I'm trying
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
but this command won't work. I get this error message
fastboot: invalid option -- 'i'.
Apparently fastboot --help also doesn't shows -i as an argument.
So how can I unlock the bootloader?
Click to expand...
Click to collapse
These are for older version adb commands so you are facing issues either use older adb files or use new commands
No longer receiving unlock files
I bought an Indian version of Z2 plus on @mazon.ae. after 2 weeks of trying and waiting for the bootloader .IMG file to unlock the phone from official zuk developer site and with different Email including [email protected] CN (aliyun) I gave up and got the device 100% refunded. The latest possible patch date is Nov 1st 2016... Anyone got better results recently (Oct Nov 2019)?
Ludo56510 said:
I bought an Indian version of Z2 plus on @mazon.ae. after 2 weeks of trying and waiting for the bootloader .IMG file to unlock the phone from official zuk developer site and with different Email including [email protected] CN (aliyun) I gave up and got the device 100% refunded. The latest possible patch date is Nov 1st 2016... Anyone got better results recently (Oct Nov 2019)?
Click to expand...
Click to collapse
Ohhh no that seems bad I just received my z2 yesterday for sake of custom rom and rooting.If this does not work out, I have to refund it ASAP.
Please follow this thread and reply if anyone got the unlock file
Finally this thread https://forum.xda-developers.com/le...-receive-unlock-bootloader-img-t3731061/page4 Post Number 40 helped me unlock my bootloader as of 16th November 2019 and now I am on custom ROM
didn't need the file at all
Phone: ZUK Z2 Plus (Z2131)
After having tried many times following this tutorial and never receiving any E-Mail, I found a rather simple solution that worked:
I didn't really expect it to work, so this is from memory, wordings may differ a bit.
First: make backup of your data!
Make sure you have updated ZUI to the latest available version.
Enable developer options ( From your device go to " About -> ZUI version" , scroll down and click " build number " continuously until you see "You are now a developer")
Go to developer Options and look for the toggle "Allow OEM Unlock" (or similar) and set it to enable. Confirm.
Reboot.
The phone automatically performs a factory reset (All Data lost!).
Now you can continue with flashing custom recovery (TWRP) and ROM.
For example use Lineage OS. Instructions: (Sorry, can't post the link) go to lineageos.org and look for the decive and go to install instructions.
Finally I can enjoy the phone with custom ROM and up-to-date Android 10.
You may have to be on ZUI 3.5 (Chinese Version) - It may not work with the Indian Version.
Follow this hints to deep flash ZUI Chinese Stock firmware: https://forum.xda-developers.com/showpost.php?p=83808887&postcount=2
Also read this:
https://forum.xda-developers.com/showpost.php?p=80890653&postcount=40
Quote:
From ZUI 3.5.xxx on you don't need unlock_bootloader.img anymore.
You need to allow OEM unlock in developer options first, then just unlock by "fastboot -i 0x2b4c oem unlock-go" .
If you did not allow OEM unlock option in developer setting then you get error message.
Click to expand...
Click to collapse
can you help me ASAP
E:\Minimal ADB and Fastboot>fastboot -i 0x2b4c flash unlock unlock_bootloader.img
target reported max download size of 1610612736 bytes
sending 'unlock' (5 KB)...
OKAY [ 0.032s]
writing 'unlock'...
FAILED (remote: Invalid data)
finished. total time: 0.072s
always like that , i've tried to get new img but still like that.
So I've installed a custom ROM in a Moto G5s because was rebooting and lagging all time (sometimes reboot several times after start). But after the experience of a custom ROM, the problems persisted, so I decided return to the original firmware.
The thing is that I reinstalled the stock firm with CMD & fastboot, but I was not be able to unlock the bootloader (despite I used neccesary comands like fastboot oem fb_mode_set fastboot oem lock begin fastboot oem fb_mode_clear fastboot oem lock repeated times). So I download motorola RSD tool and flash it with it. The process was succesfull, but my bootloader still was unlocked.
What should I do? I missed any step?
Thanks