Related
Hi Guys,
Would appreciate some help, though I realise I may be out of luck. My device is rooted with twrp installed, I thought i'd lock my bootloader so that the new killswitch / device reset protection would have some use.
Basically, it's now stuck in a boot loop. I get a flashing teamwin (twrp) logo when I try to turn it on, that's all. Here's the kicker, I can't unlock my bootloader again because I didn't have "allow OEM unlock" ticked in the developer settings.
Anyone have any ideas? I don't care if I lose my data, just panicking right now.
My Thanks!
Someone smarter than I can tell you how to use fast boot to unlock your boot loader.
TLDR: someone can help you that someone is not me. Worry not.
ixa20 said:
Hi Guys,
Would appreciate some help, though I realise I may be out of luck. My device is rooted with twrp installed, I thought i'd lock my bootloader so that the new killswitch / device reset protection would have some use.
Basically, it's now stuck in a boot loop. I get a flashing teamwin (twrp) logo when I try to turn it on, that's all. Here's the kicker, I can't unlock my bootloader again because I didn't have "allow OEM unlock" ticked in the developer settings.
Anyone have any ideas? I don't care if I lose my data, just panicking right now.
My Thanks!
Click to expand...
Click to collapse
you can try flashing the system img. can you get into the bootloader?
simms22 said:
you can try flashing the system img. can you get into the bootloader?
Click to expand...
Click to collapse
Its locked. Wont unlock because allow OEM unlock in android is unchecked. This setting is crazy
Thanks for the replies guys, anyone else got suggestions? Would motorola fix this if I sent to them? I assume they must have some development tools or qualcomm software that could do it.
ixa20 said:
Thanks for the replies guys, anyone else got suggestions? Would motorola fix this if I sent to them? I assume they must have some development tools or qualcomm software that could do it.
Click to expand...
Click to collapse
I would assume they could.
The same thing happened to me and I thought for sure I was completely shafted. Turns out you can get back into your device by doing the following:
fastboot format users
fastboot format cache
I then rebooted the phone and voila, back into Andriod where I can click that unlock setting off and try installing the custom recovery yet again.
Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.
Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.
Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking
toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.
You don't need adb.
sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)
I was gifted a Nexus 6 after my 5X died. As far as I know the device has never been OEM unlocked, much less flashed with anything. I've unlocked developer options and allowed USB debugging and OEM unlock but when I try to use power+Vol(-) to get into fastboot mode nothing happens, the screen is just black. When I bridged the device using ADB I could see the serial number and tried using the boot into recovery mode command and it rebooted to the same black screen. When I used fastboot commands on the black screen I could see the device and tried running fastboot oem unlock, it did something but wasn't successful in unlocking it. I'm not prepared to just start running fastboot commands blind like that without being able to see what's happening on the device's screen.
It's a curious problem, has anyone ever heard of it happening before? I can't find anything similar when I google it.
All I really want to do is clear the Dalvik cache and flash the latest factory image because currently, even after doing a factory reset, the device is very slow and laggy.
Is there anyway I could clear all the caches etc without going into fastboot mode or does anyone know of any fixes I could use so I can see the recovery menu?
If you boot to bootloader mode, then "fastboot boot <TWRP.img>" you might be able run twrp on your pc and clear caches. If it works, I'd consider factory resetting. You can get twrp here: https://dl.twrp.me/shamu/
I have considered that. But that requires OEM unlock, no? I still haven't managed to unlock it yet. The first time I tried, I said yes to unlock (it involves using the rocker to select a response, which I can't see the options for) but in the command window it said it failed (can't remember the error message though). I was going to try again today but because I couldn't see the options when I tried it said I'd cancelled the operation and I was too scared to try again in case something went wrong.
But, do you think I should try the fastboot oem unlock command again? I definitely need OEM unlock to install TWRP, right?
connorjolley said:
I have considered that. But that requires OEM unlock, no? I still haven't managed to unlock it yet. The first time I tried, I said yes to unlock (it involves using the rocker to select a response, which I can't see the options for) but in the command window it said it failed (can't remember the error message though). I was going to try again today but because I couldn't see the options when I tried it said I'd cancelled the operation and I was too scared to try again in case something went wrong.
But, do you think I should try the fastboot oem unlock command again? I definitely need OEM unlock to install TWRP, right?
Click to expand...
Click to collapse
To install twrp yes, you need an unlocked bootloader. This doesn't install twrp on the device. I believe it should work. It certainly shouldn't hurt. I've been unlocked since the N6 came out so I can't double check for you.
If it doesn't work, I'd be a bit inclined to just flash a factory image thus ensuring everything is stock and current. You might want to wait for others to chime in, but it's what I would do.
You may consider downloading Nexus Root Toolkit, works like a charm : ).
I can't just flash the stock bootloader without OEM unlock, right?
connorjolley said:
I can't just flash the stock bootloader without OEM unlock, right?
Click to expand...
Click to collapse
Correct, you need to be unlocked to flash a factory image, that includes the bootloader. See Google's instructions. Don't get confused by the "fastboot oem unlock"
vrs "fastboot flashing unlock" we are an older device and use oem unlock. The other is for the 6P and newer devices.
ktmom said:
Correct, you need to be unlocked to flash a factory image, that includes the bootloader. See Google's instructions. Don't get confused by the "fastboot oem unlock"
vrs "fastboot flashing unlock" we are an older device and use oem unlock. The other is for the 6P and newer devices.
Click to expand...
Click to collapse
Successfully unlocked. TWRP didn't help, still can't see the bootloader menu to access the recovery. I'm flashing the factory image now, hopefully a new bootloader will fix it. If not, is there anyway to clear the Dalvik cache using fastboot commands now the phone is unlocked?
UPDATE
Still a black screen even with a new bootloader flash. I'm assuming now this must be a hardware problem
connorjolley said:
Successfully unlocked. TWRP didn't help, still can't see the bootloader menu to access the recovery. I'm flashing the factory image now, hopefully a new bootloader will fix it. If not, is there anyway to clear the Dalvik cache using fastboot commands now the phone is unlocked?
Click to expand...
Click to collapse
I think the command is "fastboot erase cache". Also, unlocking will have wiped the device.
connorjolley said:
UPDATE
Still a black screen even with a new bootloader flash. I'm assuming now this must be a hardware problem
Click to expand...
Click to collapse
Why not just flash the entire factory image you got the bootloader from? What can it hurt? It would be really odd for this to be hardware if you can boot into the ROM and the screen works.
Hi guys, if you are like me trying to lock the bootloader to get Android Pay, or Netflix back up and running without much fuss, I found a way to lock the bootloader.
WARNING: This will do a factory reset to your device, so do backups...
Requires:
- Official OOS flashed (Download here the full zip file for the latest OOS, you can flash through TWRP or stock Recovery)
- Latest Fastboot drivers and SDK file
- Basic knowledge of Fastboot commands
Guide:
- Boot the device into Bootloader mode (power the device with Volume up + Power Button)
- Connect to the PC
- Run the command "fastboot flashing lock"
- On the device, using the volume keys select "Yes" to lock the bootoader
And that's it, the 1st boot will take longer, but just wait.
Hope this helps =)
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Titokhan said:
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Click to expand...
Click to collapse
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
hugoprh said:
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
Click to expand...
Click to collapse
Let me explore the firmware - it would a curious case of hybridization then.
Regarding the warning: Yah, my bad... missed it somehow.
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
rgreene1971 said:
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
Click to expand...
Click to collapse
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
+1
rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Why lock? Why not just use Magisk? That works fine with Android Pay.
You don't need to lock your bootloader to use Netflix
nagorimayank said:
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Click to expand...
Click to collapse
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
mullafabz said:
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
Click to expand...
Click to collapse
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
beache said:
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
Click to expand...
Click to collapse
I managed to lock back the bootloader but now am stuck in an bootloop.
mullafabz said:
I managed to lock back the bootloader but now am stuck in an bootloop.
Click to expand...
Click to collapse
You have to format data in recovery
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
sprays said:
Hi guys,
Accidentally, im locked the bootloader of my moto z3 play and i cant boot because a previous bad installation that results in a bootloop.
I cant unlock from fastboot because the acctual system is new but unbootable (usb debugging and oem unlock disable by default...
I saw that there is some toolkits for many brands and models to fix this...
Will there be any for moto z3 play? or any other way to fix this brick?
I can access fastboot and stock recovery... Can i flash anything from adb sideload?
ty in advance
Click to expand...
Click to collapse
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
sprays said:
You should be able to reflash the firmware
Use
I forgot to say that i ran by mistake flashing lock command, in way that oem is lock AND flashing too.
I have tried many times flash stock 9.0 firmware, but most part of lines out are permission denied (cause of flashing locked, i guess...)
After try flash, i get only bootloop and stock recovery.
I even already try apply update from adb sideloa to twrp or cwm but doesnt work (((
Plus, i try TOO boot on edl mode to use blank flash but doenst work, going to fastboot reason qcom boot failed ! ((((((((
I suppose can reflash the firmware with flashing locked? I have tried one of these beckham 9.0... I confess that not tried all of them.
Ty, man, for help!
Click to expand...
Click to collapse
have you tried unlocking your bootloader again?
sd_shadow said:
You should be able to reflash the firmware
Use
Code:
fastboot getvar all
To get the codename and software channel
https://mirrors.lolinet.com/firmware/moto
More in my
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
kewlzter said:
have you tried unlocking your bootloader again?
Click to expand...
Click to collapse
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
sprays said:
You should be able to reflash the firmware
Use
Yeah... But an actual rom doesnt have oem unlock neither usb debbuging actives...
Click to expand...
Click to collapse
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
kewlzter said:
Unlocking your Bootloader, you know where you enter that long code from the email that Motorola sent you.
I say this because sometimes people think, unlocking in the Dev-options, is actually unlocking the BL, when it's not.
Nor is a carrier unlock the same thing.
Your bootloader sounds locked from your Description of "access denied" errors.
I just want you to clearify that you are actually unlocked.
Click to expand...
Click to collapse
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
sprays said:
Yeah, i have the code from motorola and i try unlock with "fastboot oem unlock code", but:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
But, as i said, i cant boot o.s. to active oem unlocking.
Click to expand...
Click to collapse
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
?
kewlzter said:
Although you're on Z3, this problem is generic. Ask in the Z2 forum, as they are more active. I also think the G-series (or other popular Moto phones) forums could help you with this.
Can you get to the recovery menu, and wipe factory reset (BL->recovery, up+pwr, Wipe/Factory restore)?
Click to expand...
Click to collapse
Ty for the advice... I will do that.
Yea, i can wipe data/factory reset, but its the same. Bootloop until stuck to "fastboot reason: fall-through from normal boot mode."
I've read about this scenario for months on several different model forums and I imagine my best chance is to use the blankflash in edl mode but i can't boot into edl mode. Wherever I connect it is always recognized as a Motorola PCS or Motorola ADB device. I'm thinking of buying the deep flash cable and see if it works ...
$ fastboot getvar current-slot
//Getting and setting the slot should not cause any harm, but you never know.
$ fastboot --set-active=<a/b - whichever "current-slot" isn't.>
$ fastboot reboot
EDIT0:
In addition, you should plan ahead if you do get in. Like doing everything it takes to allow you to unlock/flash (adb).
You don't want to miss anything critical and screw up that other slot too.
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Hazardous2u said:
Moto z3 play
I have the exact same prob.... Did you ever find a fix for this?? I have tried about everything with no luck....
Click to expand...
Click to collapse
Aún no hay solución
To everyone who is having this problem, just run the command multiple times in a row and it works! I don't know why, but just running it a few times in a row (I had to do like 9 times) gave me the unlock code.
Same thing for applying the code after getting it from Moto. Had to do it like 9 times in a row again, but it worked.