Flashing Locked and can't boot - Moto Z3 Play Questions & Answers

Hello everyone,
So after messing around a bit too much with my phone, I may have finally lost him.
I was having problems updating it, so decided to try and restore it to stock, since not even factory resetting was solving the problem.
Long story short, I now have a "flashing_locked" on the bootloader menu, so if I try to flash a new one I get something like "(bootloader) check 'allow oem unlock' in developer options", but as I said, I can't get into the system. Is it possible to do this via the bootloader?
Am I doomed here? Will probably try taking it to Motorola and see if they don't mind the bootloader unlocked...
Thank you for any help
EDIT: After going through Lenovo Smart Assistant, I'm now stuck on a "Your device has loaded a differente operating system" loop. RIP I guess.

in the bootloader execute the command "fastboot oem unlock" once a message appears informing that it has lost the data and execute again the same command "fastboot oem unlock"
I hope it helps

Same thing
Code:
fastboot oem unlock
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.001s]
Finished. Total time: 0.002s

Related

Bootloader unlock FAILED (remote failure)

Hi,
I encountered problem while unlocking bootloader . After i press enter in the end of the instructions to unlock bootloader, i see a message : (bootloader) Check 'Enable OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s.
I followed the official instructions of unlocking bootloader in motorola site . Got the unlock code, and everything went fine until this point .
Any guesses ?
KabalLV said:
Hi,
I encountered problem while unlocking bootloader . After i press enter in the end of the instructions to unlock bootloader, i see a message : (bootloader) Check 'Enable OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.008s.
I followed the official instructions of unlocking bootloader in motorola site . Got the unlock code, and everything went fine until this point .
Any guesses ?
Click to expand...
Click to collapse
Which model/variant do you have?
Did you update Android?
Did you go to Settings, About Phone, Tapped Build number 7 times, to enable Developer Options?
Do you have a "OEM unlocking" option under Developer Options? Enable USB Debugging...
Boot into Bootloader Mode:
fastboot oem unlock thecodeyougot
didnt have OEM Unlocking enabled . Thanks !
check the unlock in fastboot

OEM Unlock Command Failed - "Not supported command in current status"

I recently reverted to stock so I can start from scratch and install everything over again. After all that and booting into android, I checked the ADB and OEM Unlock options in my settings. Then I rebooted into the bootloader and entered the "fastboot OEM unlock" command I followed the on-screen instructions and selected "yes" to continue. The command prompt then shows the following:
(bootloader) Unlocking bootloader...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 24.776s
I've googled this for about an hour and a half and can't seem to find an answer. Any help would be greatly appreciated.
I don't know if it's a typo, but you said you "booted into android" which to me suggests normal android system.
(which might explain why you needed adb...you don't need to enable adb for fastboot mode)
How about booting into fastboot / bootloader mode instead and try your commands there.
(press/hold power and volume down buttons to get to fastboot/bootloader mode)
Sorry if I'm misunderstanding and you are in fact attempting this in fastboot/bootloader mode.
also type a "fastboot devices" command to make sure fastboot is working between phone and pc
Someone else posted exactly this question a few months ago.
Answer? The device was already unlocked.
http://forum.xda-developers.com/nexus-6/help/help-bootloader-unlock-t3349455
I figured that might be the case. I assumed flashing the factory image also re-locked the bootloader.
You had it right. I booted the Android system. I was following the steps on the All-In-One Beginner's guide which included enabling adb. But as for me running the unlock command, I was in the bootloader when trying that.
@dahawthorne gave me the right answer in saying the device is already unlocked. Now I have a separate issue where I can't complete the rooting process, but I'll post a separate thread if I can't figure that out.

Trouble unlocking bootloader, can't select OEM unlocking

** EDIT **
I solved the problem below by updating my phone. It was a new phone, and after applying standard Motorola system updates to it that were available, I was then able to toggle the "OEM unlocking" option in developer settings.
******
I just bought a Motorola G6 and I want to unlock the bootloader on it. I followed the instructions on the Motorola website and got my bootloader unlock code. When I enter my unlock code into the fastboot command prompt I get this message back:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.000s]
Finished. Total time: 0.000s
I then booted up the phone again and enabled Developer mode. In Developer mode I see an option called "OEM unlocking", but it is off grayed out, and I can't select it. There is no way for me to toggle this on.
I did some Googling and found one thing that suggested that because it is grayed out, that means that my bootloader is actually unlocked. I don't think that is the case. When I boot back into fastboot mode, on my phone's screen it says this "oem_locked" .
Thanks for any help with this.

Fastboot remote command not allowed

I'm trying to unlock the bootloader. I got fastboot and adb to respond correctly. Here is what happens when I try:
Code:
C:\WINDOWS\system32>fastboot -i 0x0fce oem unlock 0x0FF21ECC85757B85
...
FAILED (remote: Command not allowed)
finished. total time: 0.068s
Any advice? I checked and my bootloader can be unlocked.
Aside question:
For some reason 'adb reboot fastboot' simply reboots the phone but 'adb reboot bootloader' boots into fastboot (so that fastboot devices responds correctly)
LuminousOne said:
I'm trying to unlock the bootloader. Any advice?
Click to expand...
Click to collapse
Developer options, OEM unlock - enable.
If it's greyed out then you may not be able to unlock.
Some phones sold though service providers have unlock disabled, no workround.
Didgesteve said:
Developer options, OEM unlock - enable.
If it's greyed out then you may not be able to unlock.
Some phones sold though service providers have unlock disabled, no workround.
Click to expand...
Click to collapse
My phone had the same problem showing the "OEM unlock" option greyed out.
Activating WiFi and checking for "system updates" fixed it for me, and I successfully unlocked the phone.

Can't properly re lock bootloader

Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.022s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Bootloader is now locked
OKAY [ 0.045s]
finished. total time: 0.046s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.012s]
finished. total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23537 KB)...
OKAY [ 0.618s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.678s
Click to expand...
Click to collapse
Does anyone know how to fix this?
Did you ever get this sorted ? I have the same problem on my G7 Plus. I unlocked, then loaded Lineagos, but then decided to go back to stock, I used LMSA to rescue the phone, but still got the warning and boot time "Your phone has loaded a different OS" and I can't use GPay. I tried the fastboot OEM lock (worked) and fastboot flashing lock, but I still get the warning and I can't use GPay.
I think in my case the LMSA rescue didn't work because I was originally on Android 9 and the rescue took me straing to Android 10
Elrom said:
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
Does anyone know how to fix this?
Click to expand...
Click to collapse
You can try downloading each versions from your region (RETUS, RETEU, etc) and retry the relock process until you find the correction version.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

Categories

Resources