My screen keep on showing "System Has Been Destroyed". The best I can do is to be at fastboot. When in fastboot mode I try to unlock the phone using CMD yet unsuccessfull. I can't get into developer option because it's stuck at "System Has Been Destroyed" screen.
Here's the message after input "fastboot oem device-info"
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.011s]
Finished. Total time: 0.015s
Have you flashed a rom with miflashtool? Probably you've not unchecked "clean all and lock".
I think you're phone is hard bricked
Sounds like hard brick indeed. Check this out: https://forum.xda-developers.com/showpost.php?p=80029403&postcount=22
overcustom said:
Have you flashed a rom with miflashtool? Probably you've not unchecked "clean all and lock".
I think you're phone is hard bricked
Click to expand...
Click to collapse
I have tried to flashed a rom with miflash tool. I've checked clean all only. And it showed "error FAILED (remote : Erase is not allowed in Lock State)".
Brays88 said:
I have tried to flashed a rom with miflash tool. I've checked clean all only. And it showed "error FAILED (remote : Erase is not allowed in Lock State)".
Click to expand...
Click to collapse
It means bootloader was already Locked.
On which rom were you before?
overcustom said:
It means bootloader was already Locked.
On which rom were you before?
Click to expand...
Click to collapse
I've forgot which rom i've been. Any idea how to unlock the bootloader?
Brays88 said:
I've forgot which rom i've been. Any idea how to unlock the bootloader?
Click to expand...
Click to collapse
Unfortunately you have to flash a rom using EDL mode with an authorized account, hard brick is a very awful thing.
Thats why you need to read before doing anything with your phone. Almost every thread has flashing guides and all say that you have to unlock bootloader first to flash with miflash or to flash with twrp to avoid hardbricks. Edl is the way to go, good luck mate
ef1x said:
Thats why you need to read before doing anything with your phone. Almost every thread has flashing guides and all say that you have to unlock bootloader first to flash with miflash or to flash with twrp to avoid hardbricks. Edl is the way to go, good luck mate
Click to expand...
Click to collapse
i m having same problem this morning after OTA update!!! my systeme was unlocked and everything goes well, they asked my to update i said yes as ever, but now i have screen Systeme as been Destroyed, i did everythings that i know but nothings worked, i m always blocked because any method i used to flash said can't flash, bootloader locked... WHO the [email protected]#K LOCKED MY BOOTLOADER,,,,, please help i m crying now, it's a 800 $phone useless now, my wife gonna killed me!!!! LOL
Related
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
Wait did you pull the battery while you were unlocking or after you got error?
Sent from my LG-P880 using xda app-developers app
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
Download this:
http://www.4shared.com/rar/HFf4newq/LGO4X-UNLOCK-BOOTLOADER.html
Instructions are inside
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
You did all alright, but LG does not want you to unlock, in other words your phone can not be unlocked at the moment...
Try: adb reboot oem unlock - phone on debug on, if you get red letters in top left corner LGE security...no unlock...
Did the job for 234-XXX now after reflash it is EUR-XXX...
nedooo said:
You did all alright, but LG does not want you to unlock, in other words your phone can not be unlocked at the moment...
Try: adb reboot oem unlock - phone on debug on, if you get red letters in top left corner LGE security...no unlock...
Did the job for 234-XXX now after reflash it is EUR-XXX...
Click to expand...
Click to collapse
i tried as you said adb reboot oem unlock but i dont get such tiny letters... after i tried it i checked Bootloader Unlock Check but says : Lock .
Maybe it's not my time to unlock it
the thing is it seems that the bootloader does unlock if you use the chinese kdz but the issue must be with android software not recognising it, i was on 23400 (not unlockable) and i found that the chinese kdz reported that the bootloader was unlocked, now i had the problem when trying to use unsecure boot and custom recovery so it seemed like it was still locked, now i found out the hard way that it was unlocked according to the hardware as i erased my bootloader and in the process bricked my phone
i think the problem with android recognising it is too do with something in the odm side of things,not being changed appropiatly
RuedasLocas said:
Download this:
http://www.4shared.com/rar/HFf4newq/LGO4X-UNLOCK-BOOTLOADER.html
Instructions are inside
Click to expand...
Click to collapse
I've tried this but I'm stuck at: <waiting for device>
deownagee said:
I've tried this but I'm stuck at: <waiting for device>
Click to expand...
Click to collapse
Need to install the drivers "CT_HsPhone_General_Drivers", they're inside of the folder.
If it doesn't works, don't touch the cmd window, unplug the phone and pluggit again, try all the ways.
Be creative. I had the same problem in CN V20A (also cause I didn't follow the tutorial...) but I made it.
RuedasLocas said:
Need to install the drivers "CT_HsPhone_General_Drivers", they're inside of the folder.
If it doesn't works, don't touch the cmd window, unplug the phone and pluggit again, try all the ways.
Be creative. I had the same problem in CN V20A (also cause I didn't follow the tutorial...) but I made it.
Click to expand...
Click to collapse
i was enough creative to install linux to my pc and do the whole procces on linux! And guess what: Bootloader status : Unlock ! :victory:
deownagee said:
I've tried this but I'm stuck at: <waiting for device>
Click to expand...
Click to collapse
It used to be my problem also. LMAO..
I finally succesfully unlock my phone using HTC fastboot driver.
When I got waiting for device message, I went to device manager, update fastboot driver with HTC one fastboot driver. Then my phone shows option to unlock it or not.
Sent from my LG-P880 using xda app-developers app
I would try to be as descriptive as possible.
Check if BLU allowed:
Dial *#*#7378423#*#*
Service info > Configuration > Rooting Status. It says Bootoader unlock allowed: yes
Go to SONY official webpage to get the unlock key. http://unlockbootloader.sonymobile.com/instructions
Enter the IMEI code and get the KEY in mail.
Put the phone in fastboot mode.
Code:
D:\>fastboot -i 0x0fce getvar version
version: 0.5
finished. total time: 0.002s
D:\>fastboot -i 0x0fce oem unlock 0xMYKEYINRIGHTCASE
...
FAILED (remote: Command did not succeed)
finished. total time: 0.036s
Curiously if I run the second command again, it succeeds.
Code:
D:\>fastboot -i 0x0fce oem unlock 0xMYKEYINRIGHTCASE
...
OKAY [ 0.171s]
finished. total time: 0.172s
Now if my bootloader is not supposed to be unlocked or the key is wrong then I believe the behavior should be consistent and should always FAIL. Unfortunately that is not the case. What is worse is that when now I do
Code:
D:> fastboot reboot
rebooting...
finished. total time: 0.002s
It does not reboot anymore and goes into boot loop. The only way out is to flash the stock ROM using flashtool and get it back.
What I really want to do:
Build and flash AOSP 4.3 onto the device. I have already build it and also downloaded pre-build img from one of the threads. Using fastboot flash works for boot, system and userdata on second attempt just like bootloader. However fastboot flash cache fails consistently. Rebooting again put me back into boot loop.
Is there any way to find out if the bootloader is actually unlocked or not?
I would appreciate any help in debugging/troubleshooting this problem. Looking forward.
P.S.: Not sure if this belongs here or in development forum.
bump up.
Any help would be appreciated from devs.
Go to configuration again and check rooting status. If you are truly unlocked, it will say:-
Bootloader unlocked: Yes
Sent from my C6603 using xda app-developers app
shoey63 said:
Go to configuration again and check rooting status. If you are truly unlocked, it will say:-
Bootloader unlocked: Yes
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Thanks for responding. But unfortunately for me as soon as I run the oem unlock command twice, it does not boot anymore and I have to reflash it again. Post reflash when I go back I still see the previous status.
Adding some background:
This issue occurred only after I reflashed the stock ROM using SONY companion. This might have locked the bootloader again and corrupted the process of unlocking it. Is this a possibility? Any body who had similar problem?
Could you reflash to stock and check the bootloader unlock status? If you can reflash via PC Companion, it usually means that your bootloader was not unlocked. If yours was unlocked, it would fail and you would have to use Emma instead.
pandaball said:
Could you reflash to stock and check the bootloader unlock status? If you can reflash via PC Companion, it usually means that your bootloader was not unlocked. If yours was unlocked, it would fail and you would have to use Emma instead.
Click to expand...
Click to collapse
I can reflash to stock using flashtool, does that mean anything?
Sent from my Nexus 4 using xda app-developers app
nivarp said:
I can reflash to stock using flashtool, does that mean anything?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No. If you can repair your phone via PC Companion, your bootloader is locked. Only if you are unable to do that with an error code along the lines of "This phone's software has been modified" then your bootloader is unlocked. Flashtool works regardless of bootloader unlock status.
pandaball said:
No. If you can repair your phone via PC Companion, your bootloader is locked. Only if you are unable to do that with an error code along the lines of "This phone's software has been modified" then your bootloader is unlocked. Flashtool works regardless of bootloader unlock status.
Click to expand...
Click to collapse
I can repair which essentially means that the bootloader is locked. However I still see the configuration saying bootloader unlock allowed to be yes. Strange that i am not able to unlock it.
Hi folks, saw the bootloop thread that is ongoing, but have a different issue and dont want to hjack.
I was unlocked and rooted, but then started having some constant cell signal issues.
I loaded of the toolkit, tried flashing back to stock (flash stock / unroot) > then OEM lock.
Now I cant get past the boot animation.
Can get to bootloader, fastboot works, device is LOCKED, just cant boot into the system. have left it for about 30 minutes.
I cant flash any images because I am locked, but cant unlock because I cant get into the system.
any thoughts here?
jewnersey said:
Hi folks, saw the bootloop thread that is ongoing, but have a different issue and dont want to hjack.
I was unlocked and rooted, but then started having some constant cell signal issues.
I loaded of the toolkit, tried flashing back to stock (flash stock / unroot) > then OEM lock.
Now I cant get past the boot animation.
Can get to bootloader, fastboot works, device is LOCKED, just cant boot into the system. have left it for about 30 minutes.
I cant flash any images because I am locked, but cant unlock because I cant get into the system.
any thoughts here?
Click to expand...
Click to collapse
Locked bootloader? That may be a bad situation. What happens when you try to issue: fastboot oem unlock from command prompt?
Evolution_Freak said:
Locked bootloader? That may be a bad situation. What happens when you try to issue: fastboot oem unlock from command prompt?
Click to expand...
Click to collapse
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
just saw your thread.. ugh
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
jewnersey said:
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
Click to expand...
Click to collapse
Glad you're OK. :good:
jewnersey said:
formatted cache and userdata from fastboot and got to setup.. THANK LORD JEBUS
CLOSE THREAD
Click to expand...
Click to collapse
Good job:good:
Hi everybody, I have a little question regarding my P10.
The model of my phone is VTR-L09C521B101
Is there a way to flash this phone with VTR-L09C432 version?
or i need to flash with same model version (VTR-L09C521)?
Thnks
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
M1chiel said:
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
Click to expand...
Click to collapse
thanks for the answer!!
regarding bootloader, the phone shows this:
PHONE RELOCKED
FRP LOCK
ADB shows me that the phone is unlocked, the problem is when I try to send something to phone it shows:
Error Remote command not allowed.
any ideas?
thanks!
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Quintman said:
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Click to expand...
Click to collapse
Quintman, no the phone is not listed with adb devices command. I can only enter with fastboot.
Let me paste the commands that I have tried:
C:\adb>fastboot devices
WPG7N17320000978 fastboot
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastbot oem lock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem unlock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem relock <my_unlock_code>
...
FAILED (remote: stat not match)
finished. total time: 0.016s
The Strange thing is that in the phone shows PHONE RELOCKED, not unlocked as ADB shows.
Since I uploaded boot img of another version (C432) full OTA, could this be the problem? in this case what can I do?
thanks for your help!!
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
fmm1977 said:
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
Click to expand...
Click to collapse
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Quintman said:
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Click to expand...
Click to collapse
Ok, this is what I've done step by step:
1.- With the unlock code provided by huawei, I have unlocked my phone (my version is VTR-L09C521B101 stock)
2.- Once unlocked, I have downloaded another ROM version (VTR-L29C605B151) in the web page says this rom is for latin america), so with the Huawei Update Extractor, I have extracted all files.
3.- Via ADB/FASTBOOT, I sent the files to my phone, boot.img first and then the others. (big big mistake!)
4.- Rebooted the phone, and then keeps restarting at huawei logo.
5.- Seeing that it did´t worked, what I did was to lock the phone again thinking to send it to Huawei (at this point the phone shows as "unlocked" via fastboot commands, however when I start the phone in fastboot mode, in the screen shows "PHONE RELOCKED, FRP LOCK"
6.- Sent to huawei's service, they said that they cannot fix my phone because it was tampered/rooted.
7.- Right now all I need to fix my phone is to LOCK/UNLOCK again in order to rebrand it to L29 version, since the original stock rom dont exist (not as FULL OTA).
And that´s what I did so far my friend.
Questions:
1.- Is there a way to connect to my phone and change the oem info file? or something?
2.- Do I need to wait the stock rom to be released in order to reflash via Dload method?
3.- What if the stock ROM version of my phone is never released?
thank you for your answer my friend!!
Hmm ok. I am just not sure on your step 3, I've never heard of a method that involves a boot.img... what I would suggest, is to try and download the stock firmware files (need the larger full ota files), extract the update.app file and put on sd card in \dload.
Then hold down both volume up and down and power (3 button method)
It will try and flash the stock image back to the phone.
I just tried the Dload method and nothing happened (always stuck in 5%), now im going to try to use a smaller memory card (mine is 64 Gb). lood
U have disconnected the USB cable when u try 3 button update
berka38 said:
U have disconnected the USB cable when u try 3 button update
Click to expand...
Click to collapse
Yes sr!!
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.