Database Develop

How To Unbricked A Hard Bricked Phone [ Moto X ]

How To UnBrick A Hard Bricked Moto X​
Hii , First of all I wanna thanks to this awesome scrpit by @s5610 who brought my phone from dead to alive , I think i am the first guy to unbricked the hardbricked phone using this script lol , My phone was hardbricked because i was testing my kernel and entered wrong path in partition due to which i got hard bricked i was worried for my phone , Service Center was asking for 7k in Indian Rupees , i was hopeless then i gave a try to this method , followed all steps written here and then finally i entered to fastboot menu of 30.B7 Kitkat As i was using 30.B7 Bootloader earlier and then i flashed My gpt.bin and S-partition and flashed my stock rom voilla !! and my phone booted the aim was to share this post was this method was on page 42 and only less guys have seen this post , so i created a new thread regarding this
All Credits Goes to - @s5610​
s5610 said:
Unbricking Guide for any Moto X Gen 1 (wire trick)​
Download, and unpack supplied zip to any disk, C: or D:, in root folder. Install driver by launching Qusb.drv.inst.msi, then open Windows' Device Manager, and see if you got "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
If yes, you see it, go to software part below. If it's not there, a full disassemble of the phone is needed to get close to back side of motherboard (google for "iFixit Teardown Moto X Guide" for step-by-step instruction).
So, when you are inside, disconnect the battery first. No need to pull it out, it's glued. Now get to back side of motherboard, and very very gently gain access to the lower left corner of ARM+DRAM shield (see picture). I've done it with Stanley knife. Also you can use miniature nippers - but very carefuly! Once you get access to inner space of shield, use tiny wire to short special pin to the ground (see picture), then connect USB cable, and in the moment when you see "QHSUSB_DLOAD" device (or "Qualcomm HS-USB QDLoader 9008" if driver is installed) pop out in Windows' Device Manager, quickly remove the wire. The goal is to have "Qualcomm HS-USB QDLoader 9008" in "COM & LPT ports" section of Device Manager. If it is achieved, we are done with hardware, and move on to soft part.
Now software part. Go to unzipped C:\Python27 folder, launch bat-file, and wait until finish:
RUN_blank_bootloader_flash.bat
(if you got error like "No data read from USB..." etc, just skip to next step)
Next launch either
- .Boot_KK_4.4.2_B4.exe,
or .Boot_KK_4.4.4_B7.exe,
or .Boot_LP_5.0.2_BC.exe,
or .Boot_LP_5.1.0_BD.exe,
or .Boot_LP_5.1.0_BE.exe
- depends on Android version your phone has last time. If you don't know what you need, begin with first one.
Wait 10 seconds, then launch next bat-file, and wait until finish:
RUN_moto_x_bootloader_flash.bat
Phone should go into fastboot mode! If it doesn't, repeat previous step trying higher version. But don't try to flash BC, BD, and BE, if you didn't install Lollipop on this phone!
OK. Disconnect the USB cable, connect the battery, connect again USB cable (fastboot don't work, if don't see battery). Launch next bat-file:
RUN_gpt.bin_flash.bat
The phone will get in fastboot, ready to be flashed by appropriate firmware. If it is official RSD (SBF), delete from xml strings consisting gpt.bin and motoboot.img for safe flashing.
...
Download link: http://www.mediafire.com/download/3e38rr3wy28s071/Moto.X.Unbrick.zip
This guide was brought to you by s5610
Links that this guide is based on (where I took files and general idea):
http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
http://forum.xda-developers.com/mot...-moto-x-t2629057[/url[/QUOTE][/QUOTE][/QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Not sure if additional thread is necessary )
UPDATED
The best resurrection method for Moto X is here.

Can Someone re-upload that file? Thanx!

Please upload the mediafire link...
Plz plz.. I have bricked my phone. It seems that this procedure will work for me. Please upload and save my life.

even i have bricked my moto x...need a working download link..please.

https://drive.google.com/file/d/0B3EDzuzDCakzdWxHa2RWVDJhRXc/view?usp=sharing

Cannot install qsub.drv.inst.msi on my windows 10...says failed to attribute and failed to delete qcusbser.sys.

Thanks

Can we write the full firmware through Qload 9008 mode ???

HI I have a question. I bricked my gf's phone while trying to unlock the bootloader and I am not able to turn the phone on. Only positive feedback is that when I plug it in to the computer, I can hear a notification on my computer. I followed your guide. I can see the "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
Then I followed your software instructions. When I run the RUN_blank_bootloader_flash.bat, I get the following
Code:
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
qflash - com3 is an invalid port
Invalid COM port enteredBlank flashing successful
Device will now enumerate in fastboot mode
Then, I followed the rest of the instructions by trying each .Boot .exe and waitng 10 seconds and finally with RUN_moto_x_bootloader_flash
but I am getting the following error.
Code:
C:\Users\cxx\Desktop\Python27>python qdload.py MPRG8960.bin -ptf _boot\partiti
ons.txt -pt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com3
Traceback (most recent call last):
File "qdload.py", line 815, in <module>
main()
File "qdload.py", line 762, in main
tty = openTTY(args.ttyPort)
File "qdload.py", line 174, in openTTY
tty = serial.Serial(port=tty_path, baudrate=115200)
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 38, in __init
__
SerialBase.__init__(self, *args, **kwargs)
File "C:\Python27\lib\site-packages\serial\serialutil.py", line 282, in __init
__
self.open()
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 66, in open
raise SerialException("could not open port %r: %r" % (self.portstr, ctypes.W
inError()))
serial.serialutil.SerialException: could not open port 'com3': WindowsError(2, '
The system cannot find the file specified.')
C:\Users\cxx\Desktop\Python27>pause
Press any key to continue . . .
please help.
Thanks.

Device Shows As USB Input
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks

shengslogar said:
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks
Click to expand...
Click to collapse
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.

liveroy said:
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.
Click to expand...
Click to collapse
Will do! I think I did try charging it awhile ago, but I'll give it another shot.

can my phone be unbricked?? here is the error log:
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has
een reset back to blank flash mode. Usually this is caused by power supply issu
s. Please try again with battery eliminator if it persists
Unexpected target reset, bailing out after 2 retries

I am trying to install the drivers and it will show up as qhsusb_dload for about 5 seconds then reverts back to Relink HS USB QDloader 9008. Should i try the wire trick? It will say that the Qhsusb drivers are installed but always changes.

I Bricked My Phone

Hi everyone, as you can see in topic I bricked my phone. or at least I think I did it.
To make a long story short - my brother gave me Xpera T, I installed cm12 but had problems with gapps (google apps has stopped), then I tried to remove it to have clean install and got the situation in recovery "can't mount cache/system..."
Then I tried parted /dev/block/mmcblk0 mkfs ext2
But, after I did it I restarted phone and now I can't turn it on. There is no any sign it's alive. Like a brick :-/
When I connect phone to computer and try power+up it won't enter recovery mode so I can't use ADB or Fastboot.
Only trace that phone exists shows dmesg command:
[ 135.031450] usb 3-5: new high-speed USB device number 9 using xhci_hcd
[ 135.196087] usb 3-5: New USB device found, idVendor=05c6, idProduct=9008
[ 135.196095] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 135.196100] usb 3-5: Product: QHSUSB_DLOAD
[ 135.196103] usb 3-5: Manufacturer: Qualcomm CDMA Technologies MSM
[ 135.196734] qcserial 3-5:1.0: Qualcomm USB modem converter detected
[ 135.197345] usb 3-5: Qualcomm USB modem converter now attached to ttyUSB0
So, is there any hope that I coul'd repair it, or the garbage is the right place for it?
Thank you!

Here's how to unbrick.
First turn off the phone and connect the phone to the computer while holding the volume down button. Wait for few minutes until the drivers are installed correctly. now you can disconnect the phone.
1. Download and install flashtool.
2. Download the stock rom for your device. Click here for a list of stock ROMs.
3. Right click and copy the downloaded file, and go to C:\flashtool\firmware\ and paste.
4. Open flashtool. Click the "lightning" symbol and select "flashmode" and click OK.
5. Select the file name you just downloaded, Put a tick on "No final verification" and click "flash".
6. Wait for a minute or two until you get a popup window. (It will say "press the back button and connect the phone to pc". But DO NOT do that)
7. Now turn off the phone. Connect the USB cable to the computer, but don't connect it to the phone yet.
8. Press and hold the volume down button. Keep pressing and connect the USB cable to the phone.
9. Release the volume down button as soon as the popup window go away.
10. DO NOT disconnect the USB cable until the flashtool say "Flashing completed".
11. Now unplug the cable and turn on the phone. It will take a few extra minutes to boot for the first time.
Hit the thanks button if this helped. :good:

The file I need to download is no longer available, can you upload it again?

marko-marko said:
The file I need to download is no longer available, can you upload it again?
Click to expand...
Click to collapse
Done. Checkout the post #2
All the links are updated.
Be careful what ROM you download. Double check the Model no. of your phone and the ROM. They must match.

I did everything you said until number 9 (Release the volume button as soon as the popup window go away) because that window never got away.
In flashtool windows says:
Device connected with USB debugging off
For 2011 devices line, be sure you are in MTP mode
Device disconnected
On mobile turns on red light when it's connected to USB, but turns off very soon, after flashtool says it's disconnected.

marko-marko said:
I did everything you said until number 9 (Release the volume button as soon as the popup window go away) because that window never got away.
In flashtool windows says:
Device connected with USB debugging off
For 2011 devices line, be sure you are in MTP mode
Device disconnected
On mobile turns on red light when it's connected to USB, but turns off very soon, after flashtool says it's disconnected.
Click to expand...
Click to collapse
Did you do the step 7 right? did you turn off the phone before connecting the cable?

Yes, the phone is turned off. It can't be turned on after I bricked it

marko-marko said:
Yes, the phone is turned off. It can't be turned on after I bricked it
Click to expand...
Click to collapse
I edited the instructions. Give it a try. Hope this will work :angel:

InfinitelyCrazy said:
I edited the instructions. Give it a try. Hope this will work :angel:
Click to expand...
Click to collapse
Nothing, same as the last time.
Firstly I have removed the battery for 15 minutes and than installed driver.
I followed procedure, but again number 9 never happened.
I tried to update driver for qualcomm (that is mobile) but it says that it's already updated.

OxygenOS install bricked my phone (and there are no Windows machines around)

I think I've managed to successfully brick my phone through the following process...
1. boot into recovery
2. enable sideload mode
3. adb sideload the OxygenOS beta 9 image (downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/)
Everything went smoothly and the sideload process finished successfully. Rebooted the phone, wandered away for a bit...and now it's just a black screen that won't turn on. Plugging it into my laptop I see that is identifying itself as a QUSB__BULK device:
Code:
usb 1-1.4.4: new high-speed USB device number 18 using xhci_hcd
usb 1-1.4.4: New USB device found, idVendor=05c6, idProduct=9008
usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4.4: Product: QUSB__BULK
usb 1-1.4.4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 1-1.4.4:1.0: Qualcomm USB modem converter detected
usb 1-1.4.4: Qualcomm USB modem converter now attached to ttyUSB0
What are my options at this point? All of the recovery guides I've been able to find so far start by downloading some Windows utilities, and I don't have easy access to a Windows machine.

Use the Hard Brick guide, download the full tool unbrick guide and it should work fine, follow method 2. you can find hard unbrick guide on google.

Unfortunately, the hard unbrick guide (if you mean forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/) seems to be Windows-only (it has instructions for downloading lots of Windows device drivers, etc), and as I said in my original question, I don't have a Windows machine handy.

So I have not looked alot around but I haven't seen any guides or something for Linux, but 2 ideas:
1: try that guide, maybe Linux won't need the drivers and it would work just fine.
2: you can download a windows image, install it on a Virtual Machine,unbrick your phone and then delete the VM and everything.

Is your phone's bootloader unlocked? If yes, things will much more simple.
anyway, try download full 3.2.8 ROM from OP site, boot your phone to fastboot mode and sideload it.

No OS installed, boots to TWRP but PC does not recognise device

So I've got a 3T which currently has no OS installed, just the TWRP3.2.3-0. The problem is that every time I connect the phone to the PC, the PC will only recognise the phone as Unknown USB device (Device Descriptor Request Failed). Due to this I cannot use adb to transfer files to the phone or transfer files directly to the internal storage.
I have tried using Minimal adb but device isn't found, tried different USB ports and cables too. For some reason the recovery does not read devices attached to OTG as I have also tried to transfer files using this method.
Any suggestions as to what I can do to make my PC recognise this device? Thanks

first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138

Hayatzada said:
first of all check your usb cable then use this op3/t tool
Click to expand...
Click to collapse
device isn't found, tried different USB ports and cables too
Click to expand...
Click to collapse
So yeah.
 @op USB port in the phone is damaged

Hayatzada said:
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Click to expand...
Click to collapse
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help

J-_-M-_-C said:
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
Click to expand...
Click to collapse
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now

Hayatzada said:
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Click to expand...
Click to collapse
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.

Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip

J-_-M-_-C said:
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Click to expand...
Click to collapse
please please please check your cable

johnybravo.1981 said:
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
Click to expand...
Click to collapse
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.

J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
i have the exact same problem as u my friend i had that problem so i just sideloaded my stock rom and searching for a method to fix this if u find a way to make the device recognised in twrp pls let me know

J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.

johnybravo.1981 said:
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
Click to expand...
Click to collapse
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.

J-_-M-_-C said:
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
Click to expand...
Click to collapse
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

Hayatzada said:
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.

J-_-M-_-C said:
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
Click to expand...
Click to collapse
which method do you try? i suggest full method, first one didn't worked for me .

Hayatzada said:
which method do you try? i suggest full method, first one didn't worked for me .
Click to expand...
Click to collapse
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.

J-_-M-_-C said:
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
Click to expand...
Click to collapse
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port

Hayatzada said:
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Click to expand...
Click to collapse
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.

J-_-M-_-C said:
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
Click to expand...
Click to collapse
now you should go for a hardware repair of Type C port

Hayatzada said:
now you should go for a hardware repair of Type C port
Click to expand...
Click to collapse
I already said that at the beginning.

Hardbricked when trying to install Linegae OS

Hi,
i think I hardbricked my Moto Z3 Play XT1929-8 when I tried to install Linegae OS 17.1 like described here https://forum.xda-developers.com/z3-play/development/lineage-os-moto-z3-play-t3873684 .
I successfully installed TWRP and tried to install the lineage zip from the thread with TWRP. The installation of Linegae locked successful for me. At the end of the Installation I got a message to reboot into the target System A or B where I selected B. This did not reboot instead there have been some mounting errors for 3 Partitions(I can't remember which one it was). After this TWRP asked me to reboot again. The result of this was the Hardbrick!!!
Now the device dosn't do anything when pushing the buttons. Especialy I don't get it into fastboot mode. When I connect via USB debian can't detect any device. dmesg repeats the following:
Code:
[952576.001408] usb 1-2: new high-speed USB device number 89 using xhci_hcd
[952576.129436] usb 1-2: device descriptor read/64, error -71
[952576.365420] usb 1-2: device descriptor read/64, error -71
[952576.601343] usb 1-2: new high-speed USB device number 90 using xhci_hcd
[952576.729392] usb 1-2: device descriptor read/64, error -71
[952576.965364] usb 1-2: device descriptor read/64, error -71
[952577.073403] usb usb1-port2: attempt power cycle
[952577.725243] usb 1-2: new high-speed USB device number 91 using xhci_hcd
[952577.725364] usb 1-2: Device not responding to setup address.
[952577.933337] usb 1-2: Device not responding to setup address.
[952578.141211] usb 1-2: device not accepting address 91, error -71
[952578.269197] usb 1-2: new high-speed USB device number 92 using xhci_hcd
[952578.269312] usb 1-2: Device not responding to setup address.
[952578.477351] usb 1-2: Device not responding to setup address.
[952578.685209] usb 1-2: device not accepting address 92, error -71
[952578.685294] usb usb1-port2: unable to enumerate USB device
Before I bricked my Device I got some version information via adb which might be helpful
Code:
[ro.build.version.all_codenames]: [REL]
[ro.build.version.ci]: [27]
[ro.build.version.codename]: [REL]
[ro.build.version.full]: [Blur_Version.28.11.27.beckham.retail.en.US]
[ro.build.version.incremental]: [5c49]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.qcom]: [LA.UM.6.2.r1-07200-sdm660.0]
[ro.build.version.release]: [8.1.0]
[ro.build.version.sdk]: [27]
[ro.build.version.security_patch]: [2018-04-01]
[ro.vendor.build.date]: [Sat May 5 08:17:33 CDT 2018]
[ro.vendor.build.date.utc]: [1525526253]
[ro.vendor.build.fingerprint]: [motorola/beckham/beckham:8.1.0/OPW28.70-25/5c49:user/release-keys]
[ro.vendor.build.thumbprint]: [8.1.0/OPW28.70-25/5c49:user/release-keys]
I can't understand why it hard bricked TWRP was successfully installed and if anything was wrong with the Linegae OS Installation it should boot into fastboot mode or TWRP? But the real big question is how to unbrick it? Am I right when I say the device is realy dead on any USB connection so I have to get deeper into the hardware to understand whats wrong? Could anyone help me doing this?
Best regards
Zeilentrafo

Got it to Qualcomm 9008 Mode
Ok so i played around a bit with volume down and power on and the USB problem in dmesg disappeared. Debian was now able to detect the Qualcom Chipset in 9008 Mode what is quite nice. I installed the qdl tool to flash it back to stock ROM. I although tried to talk with sahara to the Phone which worked. But I'm not sure where to get the right mbn file to flash the stock ROM? I googled around but I didn't find any site which was serious. From the unserious sites I've got a good locking firmware.
I'm not quite sure what is possible with the qdl tool and which files from the firmware have to be given? Can anyone explain this to me?
Best regards
Zeilentrafo

So you hard bricked your Beckham, and for what I read, you're using linux and now the phone is detected as Qualcomm 9008, right?
If you still unable to access the fastboot mode, I recommend you check https://forum.xda-developers.com/z3-play/how-to/how-to-restore-bricked-z3-play-t3986061.
It work for me on Ubuntu, tge Windows Qualcomm driver are really glitchy.
Once you are able to access the fastboot mode I recommend you flash this firmware first https://forum.xda-developers.com/z3-play/help/base-band-lost-brick-t3951484 (firmware in post 4).
That firmware helped me recover base band, Imei.
After that you should be good to flash whatever.
Also when usin TWRP to install Lineage, check to what slot the Lineage is being installed, normally is on the opposite slot (for A/B devices).
So when you hit the reboot on TWRP it will give you the options again to reboot system, reboot recovery or reboot slot A or slot B.
Select the one where it got flash and I then select reboot again.
You can make sure of where it got install on the aame flashing process details on TWRP