Moto Z TX1650 hard bricked - no system - oem_locked

Daniel Nascimento

New member
Feb 13, 2018
3
0
0
Rio de Janeiro
Hello everyone,

My Moto Z TX1650 was updated automatically by OTA, restart by itself and - bricked. (awesome job, Moto.)

I was going through a maze of topics until I found the blankflash script that actually owrked and made my phone trun on in fastboot again. It was in black screen no signal whatsoever even for charger - I though it was dead, but aint. (i´m posting here the blankflash used so anyone is facing the very same issue)

script to bring back your phone from dead - https://forum.xda-developers.com/attachment.php?attachmentid=4372614&d=1514473892

But now my phone is oem_locked, I dont have system (ROM) functional to enable oem in developer mode, and I cannot jump into any menu - Recovery Mode, for example, to try t o bootup using ADB, for there´s nothing in those partitions.

Recovery Mode
Startup Failed
Your device didnt start up correctly.


I´m trying to use fastboot oem unlock, I have the code, but in the end asked me to unlock it in the system.
Well if I had a system to boot into, i wasnt even trying to unlock it.

Anyone got any suggestion on how to unlock my phone OEM through fastboot only?

Thank you all.

edit:

Fastboot reason: Failed to Initialize partition table

phone specs:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.08(*)
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: 1f45b71
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 89F9DDB400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) xbl.git: xbl.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-V91.08-0-gab592a8
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.079s
 
Last edited:

Faheem1234

Member
Jul 10, 2016
16
2
0
Hello everyone,

My Moto Z TX1650 was updated automatically by OTA, restart by itself and - bricked. (awesome job, Moto.)

I was going through a maze of topics until I found the blankflash script that actually owrked and made my phone trun on in fastboot again. It was in black screen no signal whatsoever even for charger - I though it was dead, but aint. (i´m posting here the blankflash used so anyone is facing the very same issue)

script to bring back your phone from dead - https://forum.xda-developers.com/attachment.php?attachmentid=4372614&d=1514473892

But now my phone is oem_locked, I dont have system (ROM) functional to enable oem in developer mode, and I cannot jump into any menu - Recovery Mode, for example, to try t o bootup using ADB, for there´s nothing in those partitions.

Recovery Mode
Startup Failed
Your device didnt start up correctly.


I´m trying to use fastboot oem unlock, I have the code, but in the end asked me to unlock it in the system.
Well if I had a system to boot into, i wasnt even trying to unlock it.

Anyone got any suggestion on how to unlock my phone OEM through fastboot only?

Thank you all.

edit:

Fastboot reason: Failed to Initialize partition table

phone specs:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.08(*)
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: 1f45b71
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 89F9DDB400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) xbl.git: xbl.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-V91.08-0-gab592a8
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.079s
Sorry but you may have to change your motherboard because your I'm is corrupted:(
 

Lif3mau5

Senior Member
Oct 4, 2014
124
36
48
Stuttgart
You must flash a Fastboot Image with the System that was last installed on your smartphone with the right Bootloader Version or upgrade your Bootloader with the upcoming Oreo Fastboot Image.
 

Aldhair

New member
Mar 17, 2018
2
1
0
SOLUTION

INSTALL THE OFFICIAL FIRMWARE THAT YOU HAD BEFORE UPDATING OR THE MOST CURRENT FIRMWARE, WITH THAT IT IS SOLVED
IN THE PAGE "FIRMWARE CENTER"

sorry for my bad english
 
  • Like
Reactions: GiovanniNP