Relocking bootloader for sale - X 2014 Q&A, Help & Troubleshooting

Hello hopefully someone can lend me a hand. I am trying to relock my bootloader on my moto x pure edition 2014. I have downloaded the correct recovery package from Motorola directly. I issue the commands that are needed fastboot oem lock begin and then flash the firmware and then fastboot oem lock. After fastboot oem lock I get SSL error you must enter fastboot oem lock begin before lock is what is shows on the terminal windows for fastboot. On the the device screen if shows cannot validate system image although it is the correct system image. I have tried using the fastboot directly out of the Motorola software I downloaded as suggested by another user and still get the same error. I have worked on this for hours with no avail. Does anyone have any experience in this with the same problem? Thanks

Did you try following the steps listed on Motorola's website?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I believe the "fastboot oem lock begin" was only needed for older devices.

Related

Can't access full fastboot commands

Hi all, I was wondering if you know, after bootloader unlocking, why I can't access full fastboot commands as the one to remotely boot a recovery. "fastboot boot recovery.img" says "Failed: Command not allowed" and also does "fastboot oem ?" to list oem commands. OEM unlocking is permanently On , on the Dev Options and as I said before, bootloader is unlocked. But, I still can, I guess, flash boot, recovery etc. but I don't want to do it right now. I can tell it because so happened on my previous Huawei Phone and what's happening now on my P10 is the same thing. Thanks in advance.
Up, my ROM is VTR-L09C55B130 stock and I'm on Android 7.0

"FAILED (remote: unknown command)" trying to unlock bootloader

Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
This is what I get:
Code:
C:\Minimal ADB and Fastboot>fastboot devices
ZY322MF6XP fastboot
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
I updated drivers and adb and fastboot with no luck.
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
I'd double check that Allow OEM Unlock in dev options is actually on
ZeroPoke said:
I'd double check that Allow OEM Unlock in dev options is actually on
Click to expand...
Click to collapse
Tried it with it on and off twice!
Angelelz said:
Tried it with it on and off twice!
Click to expand...
Click to collapse
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
H0LT3R said:
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
Click to expand...
Click to collapse
Yeah, can't get the unique identifier though, that particular command is not working for me. Anyone have any idea why?
Hi,
For Working this command "Fastboot oem get_unlock_data"
First you need to remove or delete your phone's SCREEN LOCKS like your fingerprint, face-unlock, pattern or password etc... And keep on NONE option in lock screen. After all above procedure done than, You run that commend "Fastboot oem get_unlock_data". After runing thant command, You will not get "FAILED (remote: unknown command)"
It will work 200%.
PRUTHVIRAJ S VASUDEV said:
It will work 200%.
Click to expand...
Click to collapse
no. it doesnt.
It depends on your fastboot version. Please check "fastboot --version" and post it here.
---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------
...or try "fastboot oem help". This option will show you whether this command is available.
hi!
i have same problem.
product: Lenovo TB-7504x
fastboot getvar info:
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: WT98997_LTEROW
version-preloader: 0.1.00
version: 0.5
PS: Allow OEM Unlock in developer options is actually on
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
renforrest-EX said:
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
Click to expand...
Click to collapse
same
Did you try another USB port? Some users reported that USB 3.0 did not work but 2.0.
I would be willing to bet this is happening on devices that are not allowed to be unlocked. Like those purchased from a phone company.
its been a week since i'm trying on my htc 10, but getting the same error, i tried,
- delete the drivers and re-install
- delete sync manager
- enabled debug & oem unlock
- done reset factory for the phone
- change USB ports and cables
- tried 3 latops
nothing works, sometimes i'll just the error "waiting for any phone" and other times "FAILED (remote: unknown command)"
Angelelz said:
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
FAILED (remote: unknown command)
finished. total time: 0.000s[/CODE]
I updated drivers and adb and fastboot with no luck.
Try fastboot oem unlock first, then fastboot oem get_unlock_data
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
Click to expand...
Click to collapse
Try fastboot oem unlock first then fastboot oem get_unlock_data
I'm following a tutorial and obviously got stuck and the very same step as you did. And presumably you are following a tutorial, too.
1. Go to Security Settings and remove device lock (PIN, fingerprint, whatever you are using) and set it to NONE.
2. Go to Developer Settings and Unlock Bootloader. (If you skip step 1., you'll be asked to unlock your device here, but find that the Unlocking failed afterwards. Hence, go to step 1. and remove the lock first.)
3. fastboot oem unlock
Done. (Bootloader is unlocked now. Confirm via boot to fastboot mode (Volume down + Power button))
fastboot oem get_unlock_data is probably removed (deprecated) and maybe you don't even need a key from the manufacturer to unlock anymore.
gelignite said:
maybe you don't even need a key from the manufacturer to unlock anymore.
Click to expand...
Click to collapse
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
WoKoschekk said:
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
Click to expand...
Click to collapse
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
gelignite said:
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
Click to expand...
Click to collapse
Moto E4 is a developer's device without a locked bootloader. I thought you were talking about a Moto G6.
Baronstragen said:
Try fastboot oem unlock first then fastboot oem get_unlock_data
Click to expand...
Click to collapse
fastboot oem unlock worked for me

Bootloop, flash locked. What can I do?

Short story: my phone bootloops (shows the Android One screen for 3 seconds, then reboots), and I cannot unlock the flash in fastboot. fastboot oem unlock fails, fastboot flashing unlock fails, fastboot flashing critical_unlock fails.
What can I do, is my phone definitely bricked?
Long story: I installed september OTA and then rooted with Magisk using the image patch method. Now I wanted to get October OTA, so uninstalled Magisk to recover the unpatched bootloader, but the OTA refused to install. So I tried the flash_all method, but it failed because I did not do the critical unlock. So I tried the fastboot flash critical_unlock, but it continuously refused to work.
So I decided to agan lock flash, and do the oem lock, to restart the unlock procedure from the beginning. But after locking, the phone does not boot anymore (and it was booting fine before!). On top of that, I cannot oem unlock anymore, fastboot oem unlock always fails.
Is there any way to recover the phone?
Try fastboot oem edl
then use mi flash
Thanks for help.
Unfortunately fastboot oem edl fails:
Code:
# fastboot oem edl
FAILED (remote: Device is already locked!)
Finished. Total time: 0.001s
And as fastboot oem unlock also fails, I cannot unlock the bootloader.
doragasu said:
Thanks for help.
Unfortunately fastboot oem edl fails:
And as fastboot oem unlock also fails, I cannot unlock the bootloader.
Click to expand...
Click to collapse
I'll need more info than that
what's the error you get when using oem unlock or unlock_critical?
are you using minimal adb? If so, don't, use this instead https://developer.android.com/studio/releases/platform-tools
Are you using a usb 3.0 port? Switch to a usb 2.0 if you are
I am working from Linux, and I have the full Android Studio installed. I cannot use adb, since I cannot boot the phone (and as far as I know, adb does not work on fastboot, but I might be wrong).
I will try with the one you linked and come back with the results.
doragasu said:
I am working from Linux, and I have the full Android Studio installed. I cannot use adb, since I cannot boot the phone (and as far as I know, adb does not work on fastboot, but I might be wrong).
I will try with the one you linked and come back with the results.
Click to expand...
Click to collapse
Minimal adb includes fastboot, if you have minimal adb or you installed it from the repo then it's outdated, use the one I linked
Nothing was working for me, so finally I recovered the phone by opening it and using the deep flash method.

Trouble with unlocking bootloader

Hi everyone, I recently decided to root my One Power XT1942-2 using Magisk. However, I'm stuck on the first step of unlocking the bootloader. The guides I've seen on this forum have basically been the following simple steps:
1. fastboot oem get_unlock_data
2. Take the unlock code, edit it into a single string, and send it to Motorola using their website.
3. Take the unlock code and run: fastboot oem unlock [unlock code]
Now, I haven't even been able to run the first command as fastboot just hangs. I rebooted into fastboot mode and verified that the device was connected (the serial number appears when running "fastboot devices"), but when running "fastboot oem get_unlock_data", the program just hangs.
Here are the device details:
Stock ROM (obviously)
May 1st security patch
USB Debugging and OEM unlocking enabled (checked and double-checked)
PC details:
Arch Linux (kernel 5.1.15-arch1-1-ARCH), x86_64
Using latest Android Platform Tools, as of June 28, 2019.
android-udev package installed.
I've also attempted doing the same on a Windows 10 PC, but to no avail. Is anybody else facing this issue, or is there something important I'm missing? TIA
I have used motorola 3G two times and 2G once i tried to unlock bootloader i hot same issue what u have to do are follow the all steps correctly find out form of moto 3G and try to unlock ur phone again theres something wrong like u are not opening the cmd command in same folder where u installed the adb fastboot

Question How to UNLOCK BOOTLOADER UNOFFICIALLY ?

Greetings!
As far as I know ASUS does not have a physical bootloader unlock counter like Samsung smartphones with their KNOX. This means that ASUS gets information about the unlocked bootloader via the internet when using their official unlock bootloader app. That is, ASUS gets the IMEI or S/N of the smartphone and puts it on their blacklist.
Is there any way to unlock the bootloader unofficially?
I really want to be able to get the bootloader back to its locked state and start getting and installing updates from my smartphone without using a PC as it was before the bootloader manipulation.
I tried these adb commands, but they don't work.
fastboot oem unlock
fastboot oem unlock confirm
fastboot oem asus-go
fastboot oem asus-go confirm
fastboot oem get_unlock_key
fastboot flashing unlock
fastboot oem asus-unlock working but i got error Verify unlock token fail.

Categories

Resources