How to restore a bricked Z3 Play

[rocktone]

Hello,

If you're like me, you may have accidentally flashed and wiped your partitions, including the bootloader, causing your device to become an expensive doorstop or paperweight.

First of all, take a deep breath.

Second of all, you can use blankflash to fix it and allow the phone to boot back to the bootloader.

1. Check if your phone is detected. On Linux, your phone will be listed in lsusb as a QUALCOMM MODEM (or something close to that). That means your phone is not truly dead!
2. Go to https://mirrors.lolinet.com/firmware/moto/beckham/blankflash
3. Download the zip file there
4. Save it somewhere
5. unzip the file
6. If you're using Linux (you should be), this is easy at this point. Plug the phone in, and run ./blankflash.sh
7. The terminal will flash and say that it's attempting to poll /dev/ttyUSB0 (or something similar). This is a good sign. Linux, unlike Windows, will let you directly write to a raw USB device. On Windows you'll have to install buggy QUALCOMM drivers that never seemed to work for me. (not that it won't work for you, but I wouldn't bet on it)
8. It's likely that the flash will fail. Keep trying. Hold down the power and volume down buttons and keep holding it down.
9. Eventually, it should work and you'll see that the phone has been flashed. Your phone will boot to a weird looking bootloader screen. Once that happens, you are done. If you reboot the phone, it'll boot to the same screen, and you can simply use fastboot for the rest.

I hope this helps someone. I spent 4 hours trying to get my device to rise again from the grave. If I can save one other person from this same issue of trying to find a working blankflash, then it'll be worth it!.

 

[TheWerewolf]

Actually, for the record, Windows most certainly lets you write directly to a raw USB device. Just not the way Linux or Unix does it.

In any case, the blankflash.sh script just runs qboot - which is exactly what the Windows version does except it runs qboot.exe.

 

[j_cesarbm]

Hello,

If you're like me, you may have accidentally flashed and wiped your partitions, including the bootloader, causing your device to become an expensive doorstop or paperweight.

First of all, take a deep breath.

Second of all, you can use blankflash to fix it and allow the phone to boot back to the bootloader.

1. Check if your phone is detected. On Linux, your phone will be listed in lsusb as a QUALCOMM MODEM (or something close to that). That means your phone is not truly dead!
2. Go to https://mirrors.lolinet.com/firmware/moto/beckham/blankflash
3. Download the zip file there
4. Save it somewhere
5. unzip the file
6. If you're using Linux (you should be), this is easy at this point. Plug the phone in, and run ./blankflash.sh
7. The terminal will flash and say that it's attempting to poll /dev/ttyUSB0 (or something similar). This is a good sign. Linux, unlike Windows, will let you directly write to a raw USB device. On Windows you'll have to install buggy QUALCOMM drivers that never seemed to work for me. (not that it won't work for you, but I wouldn't bet on it)
8. It's likely that the flash will fail. Keep trying. Hold down the power and volume down buttons and keep holding it down.
9. Eventually, it should work and you'll see that the phone has been flashed. Your phone will boot to a weird looking bootloader screen. Once that happens, you are done. If you reboot the phone, it'll boot to the same screen, and you can simply use fastboot for the rest.

I hope this helps someone. I spent 4 hours trying to get my device to rise again from the grave. If I can save one other person from this same issue of trying to find a working blankflash, then it'll be worth it!.

Grace and Peace my friend. Thank you very much for your help. With your help I was able to recover my MOTO Z3 Play. God bless you.

 

[ftagnome]

Still bricked Z3Play

Hello -
Here's my situation - I've got a bricked Z3 Play. It was rooted, with twrp-3.3.1-1-beckham installed, though the recovery screen never worked right after that - only brought up the splash screen.
All was well until I tried to install XPosed Framework.
Now my phone won't boot (bootloop), and as I mentioned already, TWRP doesn't work - it gets stuck on the splash screen.
From the Fastboot screen, I can execute some fastboot commands (fastboot version 29.0.5-5949299) however can't flash - it fails.
From the (frozen) TWRP screen, I can execute ADB (Android Debug Bridge version 1.0.41 / Version 29.0.5-5949299). I can even get an ADB shell and see the phone's filesystem.
QBoot (Motorola qboot utility version 3.40) never finds any device.
I have installed the latest Moto drivers from their site. I'm running Windows 10, in TEST mode.
Any help would be greatly appreciated!
Thank you.

 

[kewlzter]

Hello -
Here's my situation - I've got a bricked Z3 Play. It was rooted, with twrp-3.3.1-1-beckham installed, though the recovery screen never worked right after that - only brought up the splash screen.
All was well until I tried to install XPosed Framework.
Now my phone won't boot (bootloop), and as I mentioned already, TWRP doesn't work - it gets stuck on the splash screen.
From the Fastboot screen, I can execute some fastboot commands (fastboot version 29.0.5-5949299) however can't flash - it fails.
From the (frozen) TWRP screen, I can execute ADB (Android Debug Bridge version 1.0.41 / Version 29.0.5-5949299). I can even get an ADB shell and see the phone's filesystem.
QBoot (Motorola qboot utility version 3.40) never finds any device.
I have installed the latest Moto drivers from their site. I'm running Windows 10, in TEST mode.
Any help would be greatly appreciated!
Thank you.

Fastboot "boot" into older version of TWRP?

 

[sprays]

In my case, lsusb found my moto z3 play as a "Motorola PCS"

Because of this, i guess, the ./blank-flash.sh stuck in "<waiting for device>"

Its mean i need install a driver? im using distro Deepin 15.10.1

 

[eric.new.master]

Aun tendras el loader.img que me lo puedas proporcionar?

 

[KageCM]

Sorry for the length. TL;DR: It was the USB-C cable/slot. Needed a USB-A to C or the USB-A slot

I ran into a problem trying to fix a hard brick so I'm posting what happened to me and what finally worked just incase anyone else runs into this kind of problem. First heres what got me into trouble. Now instead of wiping out a partition, I was trying to make backups of Slots A and B before doing anything. I had finished Slot A and was typing in my preferred backup naming for B when TWRP just restarted. I figured something might be bugging so I opted to reboot the Recovery. BIG mistake. I ended up switching to the empty B partition, which I didn't realize for many hours.

I was stuck with hard brick, the phone showed up as a QUALCOMM MODEM like rocktone said, but blankflash kept not finding the phone.

[ -0.000] Opening device: \\.\COM9
[  0.006] Detecting device
[ 34.020] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.020] Check qboot_log.txt for more details
[ 34.021] Total time: 34.022s
[ 34.021] 
[ 34.021] qboot version 3.86
[ 34.021] 
[ 34.021] DEVICE {
[ 34.021]   name  = "\\.\COM9",
[ 34.021]   flags = "0x64",
[ 34.021]   addr  = "0x28FD74",
[ 34.021]   api.bnr = "0x482CE0",
[ 34.021] }
[ 34.021] 
[ 34.021] 
[ 34.021] Backup & Restore {
[ 34.021]   num_entries = 0,
[ 34.021]   restoring = "false",
[ 34.021]   backup_error = "not started",
[ 34.021]   restore_error = "not started",
[ 34.021] }
[ 34.021]

I went as far as trying a making a bootable live usb of linux, which I have no experience with, trying to fix this and getting almost the same thing.

[  0.000] Opening device: /dev/ttyUSB0
[  0.000] ERROR: device_open()->error opening device
[  0.000] Check qboot_log.txt for more details
[  0.000] Total time: 0.000s
[  0.000] 
[  0.000] qboot version 3.86
[  0.000] 
[  0.000] DEVICE {
[  0.000]   name  = "/dev/ttyUSB0",
[  0.000]   flags = "0x60",
[  0.000]   addr  = "0x161C5A60",
[  0.000]   serial_nix.device_pathname = "/sys/bus/usb/devices/4-1/4-1:1.0/ttyUSB0",
[  0.000]   api.bnr = "0x13D03D0",
[  0.000] }
[  0.000] 
[  0.000] 
[  0.000] Backup & Restore {
[  0.000]   num_entries = 0,
[  0.000]   restoring = "false",
[  0.000]   backup_error = "not started",
[  0.000]   restore_error = "not started",
[  0.000] }
[  0.000]

It was still a couple hours later of banging my head against a wall that finally made me think of switching from USB-C cable/slot I was using (this phone is my first experience using USB-C) to a USB-A to C cable/slot. I was so confused trying to get linux to work and it kept hanging so I rebooted to windows and blankflash worked the first time with the cable/slot switch. Hopefully this is helpful to someone down the line.

TL;DR: It was the USB-C cable/slot. Needed a USB-A to C or the USB-A slot

 

[Yayo70136]

help!!!! the bootloader is corrupt and does not allow me to update it with any rom so I cannot repair the radio signal of my phone so I thought I would use the blankflash file to repair the boot loader and be able to update with stock rom but I don't know how a hard brick could be caused in my moto z3 play currently, I can enter fastboot mode and flash any rom beckham and the cell phone works but without signal and without wifi: / any ideas ??? Any help is appreciated !!!! I've been like this for almost a month!



fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) product: beckham
(bootloader) board: beckham
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM636 1.0 (1)
(bootloader) serialno: ZY2...........
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 1FB614B6
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ..................
(bootloader) meid:
(bootloader) date: 09-14-2018
(bootloader) sku: XT1929-6
(bootloader) carrier_sku: XT1929-6
(bootloader) battid: SB18C20117
(bootloader) battery-voltage: 3890
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/beckham/beckham:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 131-27-1-22/d2da2:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.271.29.beckham.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-05500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gebfe3c50a253
(bootloader) kernel.version[1]: -02598-g4bfe89b274ac ([email protected]
(bootloader) kernel.version[2]: 2) (gcc version 4.9.x 20150123 (prerelea
(bootloader) kernel.version[3]: se) (GCC) ) #1 SMP PREEMPT Thu Mar 12 22
(bootloader) kernel.version[4]: :35:14 CDT 2020
(bootloader) git:abl: MBM-3.0-beckham_sprint-43c7c77-190708
(bootloader) git:xbl: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) gitmic: MBM-3.0-beckham_sprint-abcb4b6-190708
(bootloader) git:rpm: MBM-3.0-beckham_sprint-33b79ec-190708
(bootloader) git:tz: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:hyp: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:devcfg: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:cmnlib64: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:keymaster: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) gitrov: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) git:storsec: MBM-3.0-beckham_sprint-c3fd846-dirty-190708
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: attmx
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.146s


ayudaaa!!!!!!!!:llorando::llorando::llorando:

 

[moonlightdrive]

Thanks, it worked on the first try and literally took 5 secs. (setup: Windows 10 64-Bits), i did not download a particular Qualcomm driver, just plug the dead device and Windows recognized it as QHUSB_BULK. Again, thank you.

 

[gwalborn]

I have also "hard bricked" my Moto Z3 Play while trying to install TWRP recovery. The phone is is "Qualcomm" mode and I am trying to use blankflash from Linux. It seems that it's TRYING to flash the bootloader, but it fails with the following log entries:

**** Log buffer [000001] 2020-07-22_19:10:53 ****

[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Detecting device
[ 5.710] ...cpu.id = 204 (0xcc)
[ 5.710] ...cpu.sn = 1760558744 (0x68effe98)
[ 5.710] Opening singleimage
[ 5.710] Loading package
[ 5.715] ...filename = pkg.xml
[ 5.717] Loading programmer
[ 5.718] ...filename = programmer.elf
[ 5.718] Sending programmer
[ 5.891] Handling things over to programmer
[ 5.891] Identifying CPU version
[ 5.891] Waiting for firehose to get ready
[ 8.910] ...SDM636 1.0
[ 8.910] Determining target secure state
[ 8.913] ...secure = yes
[ 8.966] Configuring device...
[ 8.975] Flashing GPT...
[ 8.975] Flashing partition with gpt.bin
[ 8.983] Initializing storage
[ 9.065] ...blksz = 512
[ 11.341] Target NAK!
[ 11.341] ...INFO: Device Total Logical Blocks: 0x2000
[ 11.342] ...INFO: Device Total Physical Partitions: 0x4
[ 11.342] ...INFO: Device Manufacturer ID: 0x15
[ 11.342] ...INFO: Device Serial Number: 0xdc246a2b
[ 11.342] ...INFO: {"storage_info": {"total_blocks":8192, "block_size":512, "page_size":512, "num_physical":4, "manufacturer_id":21, "serial_num":3693373995, "fw_version":"5","mem_type":"eMMC","prod_name":"DH6DMB"}}
[ 11.342] ...eMMC Extended CSD Revision: 0x8
[ 11.342] ...eMMC Firmware Version: 0x5
[ 11.342] ...eMMC_RAW_DATA [0:265]000000000000000000000000000000003900000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000F0000C8C80000000000000000000000000000000000000000000000000000000000000000050000000000000000F80A0000000000000000000000000000000000000100000000000000000000000000000000000000000000000000008F0E00070001020000141F20000000000000000000000000000000010000000000000008000200571F0A0200000000000000000000000100C0470707110007071001010107200007111B550200000000000000001E00000000003C0A0000010000050000000000000000000110
[ 11.342] ...eMMC_RAW_DATA [266:531]00010101000000000000000000000000000000000000000000000000000000000000000000000000000F0100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000081C70000030307050002013F3F0101010000000000000044000115320127D0FF03590FEFFFDBF60040408E
[ 11.342] ...ERROR: XML not formed correctly. Expected a < character at loc 0
[ 11.342] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 11.342] Check qboot_log.txt for more details
[ 11.342] Total time: 11.342s
[ 11.342]
[ 11.342] qboot version 3.86
[ 11.342]
[ 11.342] DEVICE {
[ 11.342] name = "/dev/ttyUSB0",
[ 11.342] flags = "0x140",
[ 11.342] addr = "0xFAABBFF0",
[ 11.342] serial_nix.device_pathname = "/sys/bus/usb/devices/1-1.1.2/1-1.1.2:1.0/ttyUSB0",
[ 11.342] sahara.current_mode = "0",
[ 11.342] api.buffer = "0x7F1A18828010",
[ 11.342] cpu.serial = "1760558744",
[ 11.342] cpu.id = "204",
[ 11.342] cpu.sv_sbl = "0",
[ 11.342] cpu.name = "SDM636",
[ 11.342] storage.type = "eMMC",
[ 11.342] sahara.programmer = "programmer.elf",
[ 11.342] module.firehose = "0x21C70E0",
[ 11.342] api.firehose = "0x21D0190",
[ 11.342] cpu.ver = "256",
[ 11.342] cpu.vername = "1.0",
[ 11.342] fh.max_packet_sz = "1048576",
[ 11.342] fh.storage_inited = "1",
[ 11.342] }
[ 11.342]

I have also tried to find a "loader.img" file for the Moto Z3 Play to try an SD card recovery, but I have not been able to find one. What is the difference between a loader.img file and a bootloader.img file? I have Moto Z3 Play stock ROMs. Is it possible to generate a loader.img file?

Thanks in advance,

gwalborn

 

[Redman3000]

Hopefully helps

Hello -
Here's my situation - I've got a bricked Z3 Play. It was rooted, with twrp-3.3.1-1-beckham installed, though the recovery screen never worked right after that - only brought up the splash screen.
All was well until I tried to install XPosed Framework.
Now my phone won't boot (bootloop), and as I mentioned already, TWRP doesn't work - it gets stuck on the splash screen.
From the Fastboot screen, I can execute some fastboot commands (fastboot version 29.0.5-5949299) however can't flash - it fails.
From the (frozen) TWRP screen, I can execute ADB (Android Debug Bridge version 1.0.41 / Version 29.0.5-5949299). I can even get an ADB shell and see the phone's filesystem.
QBoot (Motorola qboot utility version 3.40) never finds any device.
I have installed the latest Moto drivers from their site. I'm running Windows 10, in TEST mode.
Any help would be greatly appreciated!
Thank you.

I don't know if the info will still be helpful, but I booted TWRP 3.4.0-0 and works fine with Z3 play. I haven't tried to flash it, I just " fasboot boot " it.

 

[Redman3000]

Hello,

If you're like me, you may have accidentally flashed and wiped your partitions, including the bootloader, causing your device to become an expensive doorstop or paperweight.

First of all, take a deep breath.

Second of all, you can use blankflash to fix it and allow the phone to boot back to the bootloader.

1. Check if your phone is detected. On Linux, your phone will be listed in lsusb as a QUALCOMM MODEM (or something close to that). That means your phone is not truly dead!
2. Go to https://mirrors.lol inet.c om/firmware/moto/beckh am/blankflash
3. Download the zip file there
4. Save it somewhere
5. unzip the file
6. If you're using Linux (you should be), this is easy at this point. Plug the phone in, and run ./blankflash.sh
7. The terminal will flash and say that it's attempting to poll /dev/ttyUSB0 (or something similar). This is a good sign. Linux, unlike Windows, will let you directly write to a raw USB device. On Windows you'll have to install buggy QUALCOMM drivers that never seemed to work for me. (not that it won't work for you, but I wouldn't bet on it)
8. It's likely that the flash will fail. Keep trying. Hold down the power and volume down buttons and keep holding it down.
9. Eventually, it should work and you'll see that the phone has been flashed. Your phone will boot to a weird looking bootloader screen. Once that happens, you are done. If you reboot the phone, it'll boot to the same screen, and you can simply use fastboot for the rest.

I hope this helps someone. I spent 4 hours trying to get my device to rise again from the grave. If I can save one other person from this same issue of trying to find a working blankflash, then it'll be worth it!.

Good Morning kind human... I think,
So I finally bricked my Beckham device and I've been trying this blankflash that you speak of... Thru Windows 10, and exactly as you said the drivers seem to glitch at the moment of running the blankflash. exe. they are detecting the Qualcomm 9008 but goes in and out.
I want to try it on a Linux, don't know much about it but I know how to read. What I want to know if I could try it with the WSL or if there is an actual desktop with Linus as the OS.
I had the understanding that because of all the flavors available for Linux there was no actual desktop.
I search a bit about how to use it, but don't know how to get my hands on it other than WSL.
would you mind helping on this inquiry?

 

[Redman3000]

Good Morning kind human... I think,
So I finally bricked my Beckham device and I've been trying this blankflash that you speak of... Thru Windows 10, and exactly as you said the drivers seem to glitch at the moment of running the blankflash. exe. they are detecting the Qualcomm 9008 but goes in and out.
I want to try it on a Linux, don't know much about it but I know how to read. What I want to know if I could try it with the WSL or if there is an actual desktop with Linus as the OS.
I had the understanding that because of all the flavors available for Linux there was no actual desktop.
I search a bit about how to use it, but don't know how to get my hands on it other than WSL.
would you mind helping on this inquiry?

Nevermind... Did a bit of research and I'm dual booting Ubuntu.
Just having a bit of hard time installing the Realtek 8821cd Wi-fi driver

 

[Mcdan333]

Bricked Z3 Play here. Blankflash runs to completion, ending with the following messages in verbose mode:

[  9.098] D->H: log value="Inside handlePower() - Requested POWER_RESET_TO_FASTBOOT"
[  9.098] D->H: log value="Issuing bsp_target_reset_fastboot() after 1 seconds"
[  9.098] D->H: response value="ACK" 
[  9.098] Total time: 9.098s

On reboot, it never gets to fastboot mode. The Motorola splash screen blinks 3 times and then goes blank. The device continues to be recognized by Linux as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I've tried blankflashing it dozens of times now with the same result. Am I screwed?

 

[Redman3000]

Hello,

If you're like me, you may have accidentally flashed and wiped your partitions, including the bootloader, causing your device to become an expensive doorstop or paperweight.

First of all, take a deep breath.

Second of all, you can use blankflash to fix it and allow the phone to boot back to the bootloader.

1. Check if your phone is detected. On Linux, your phone will be listed in lsusb as a QUALCOMM MODEM (or something close to that). That means your phone is not truly dead!
2. Go to https://mirrors.lolinet.com/firmware/moto/beckham/blankflash
3. Download the zip file there
4. Save it somewhere
5. unzip the file
6. If you're using Linux (you should be), this is easy at this point. Plug the phone in, and run ./blankflash.sh
7. The terminal will flash and say that it's attempting to poll /dev/ttyUSB0 (or something similar). This is a good sign. Linux, unlike Windows, will let you directly write to a raw USB device. On Windows you'll have to install buggy QUALCOMM drivers that never seemed to work for me. (not that it won't work for you, but I wouldn't bet on it)
8. It's likely that the flash will fail. Keep trying. Hold down the power and volume down buttons and keep holding it down.
9. Eventually, it should work and you'll see that the phone has been flashed. Your phone will boot to a weird looking bootloader screen. Once that happens, you are done. If you reboot the phone, it'll boot to the same screen, and you can simply use fastboot for the rest.

I hope this helps someone. I spent 4 hours trying to get my device to rise again from the grave. If I can save one other person from this same issue of trying to find a working blankflash, then it'll be worth it!.

It worked man!!
It's Alive... I had to learn the basics of linux and ended up loving it.
Thank you very much! if I wasn't as broke I would def donate something XD

 

[Yayo70136]

z3 play without OS and bootloader blocked

I hope I can get some help.. hello I have a z3 play bike without operating system, and it has the bootloader locked.. I have the key to disable it but there is no system to enter and enable "oem" I do not know what I can do in this case? does not go from fastboot mode and if you start the terminal a message comes out: your device is corrupt and will not boot "" so I thought blankflash. but he's not totally dead. someone who can help me? I've been looking for some solution but there doesn't seem to be any... try flashing the latest version available but there is only error. "permission denied" !!! I can't think of anything else! any ideas? a greeting and thank you in advance

 

[KageCM]

I hope I can get some help.. hello I have a z3 play bike without operating system, and it has the bootloader locked.. I have the key to disable it but there is no system to enter and enable "oem" I do not know what I can do in this case? does not go from fastboot mode and if you start the terminal a message comes out: your device is corrupt and will not boot "" so I thought blankflash. but he's not totally dead. someone who can help me? I've been looking for some solution but there doesn't seem to be any... try flashing the latest version available but there is only error. "permission denied" !!! I can't think of anything else! any ideas? a greeting and thank you in advance

Have you unlocked Developer Mode? Going off of memory since its baked into the ROM I'm using. Under the Settings menu look for 'About Phone'. In there look for 'Build Number'. Tap on in multiple times till it says 'you are now a Developer'. There should now be a new menu in Settings that called 'Developer Options'. Look in there for 'OEM unlock'.

 

[Yayo70136]

[/COLOR]

Have you unlocked Developer Mode? Going off of memory since its baked into the ROM I'm using. Under the Settings menu look for 'About Phone'. In there look for 'Build Number'. Tap on in multiple times till it says 'you are now a Developer'. There should now be a new menu in Settings that called 'Developer Options'. Look in there for 'OEM unlock'.

Good morning , the problem is that I don't have an operating system. It does not enter the system at all, it only reboots in fastboot mode and the bootloader is blocked .... although I have the motorola unlock code .. when trying to unlock it tells me that I should check the oem unlock in the programmer options as you mentioned ... but as I said I don't have SO ... what other option do I have?

 

[kewlzter]

[/COLOR]








Good morning , the problem is that I don't have an operating system. It does not enter the system at all, it only reboots in fastboot mode and the bootloader is blocked .... although I have the motorola unlock code .. when trying to unlock it tells me that I should check the oem unlock in the programmer options as you mentioned ... but as I said I don't have SO ... what other option do I have?

how do you know that you don't have an O/S? Have you tried booting into Recovery, and selecting factory reset?