Develop Bugs

Defy bricked (completely?)

hi, yesterday i just bought a bricked motorola defy, since i read that was almost imposible to brick one...i thought it'd be easy to unbrick
ill explain:
black screen, no recovery, no bootloader mode....
theorically it had android 2.2
when i conect it to the pc it connects and instantly disconects (someone posted the same and he said that randomly it'd connect succesfully)
battery shows 4v (so itd flash)
white led shows up when i connect the usb without battery and turns off when i put the battery
rsd cant recognise it (windows neither)
also tried a linux script, but it neither recognises it...
i thought id be an uncharged battery + wrong sbf
but i cant get it to connect...
id apreciate fast responses

May be your battery will b low....Try to charge it and than try...
Sent from my MB525 using XDA App

i already charged it with the mvgyber fix... i guess the red cable goes to the + (top right) and the black to the - (top left...)
if so, i tried.

also tried a linux script, but it neither recognises it...
Click to expand...
Click to collapse
What script did you use?
Is it sbf_flash? Please give us more details! Like the name of the script/binary file you used, the parameters passed at runtime, the error you received after running the script/binary tool.
Did you tried to see if any information is added in the linux log files while connecting the phone to your computer using a "microUSB to USB" cable?

i tried the sbf_flash one, (there are others?)
it says, waiting for phone... or something like that...(i dont have linux here)
if the battery shows 4v it isnt a battery issue am i right?

Not as far as I know, but sbf_flash is a binary tool and since you said that you have tried a linux script I thought that you are using something else.
Basically, when a device is connected to a computer running linux, via USB, you can find informations about the attached device in some log files (/var/log/messages or /var/log/udev).
If/when you will have a linux around, let me know and I'll try to help you (if I can).

tomorrow ill have linux access, ill post logs...
btw... has nobody seen a solution for the connecting-disconeccting issue? ive seen few posts with it, but anyone posts a solution, just someone saying is luck...
i thought electronics had no true randomness,

im getting this at /var/log/messages
May 12 08:11:01 ubuntu kernel: [ 1192.928137] usb 1-6: new high speed USB device using ehci_hcd and address 9
May 12 08:11:01 ubuntu kernel: [ 1193.062719] usb 1-6: configuration #1 chosen from 1 choice
May 12 08:11:04 ubuntu kernel: [ 1196.056253] usb 1-6: USB disconnect, address 9
May 12 08:11:17 ubuntu kernel: [ 1209.308069] usb 1-6: new high speed USB device using ehci_hcd and address 10
May 12 08:11:17 ubuntu kernel: [ 1209.442678] usb 1-6: configuration #1 chosen from 1 choice
May 12 08:11:20 ubuntu kernel: [ 1212.436317] usb 1-6: USB disconnect, address 10
at udev, i cant see anything related to the phone...

Those messages appear in the log file exactly when the phone is connected to the computer?
In my /var/log/messages other information appears when the phone is plugged in (like device manufacturer, device serial number etc) but all my log messages go into /var/log/messages (I'm using Gentoo at home), but in Ubuntu it seems that most of these messages go to /var/log/udev.
What version of sbf_flash did you use? The last version is 1.23 (mbm).
A few days ago I came across an article describing the udev configuration in order to be able to connect to the phone using adb. I don't know if this will help you since USB debugging must be turned on and for that you need a running android device. I'll send you the link via PM since I do not have enough posts in this forum to be allowed to write url's in the post.

ill post the last lines of the udev log, at night (3h actually)
but somehow i dont know why, but the behaviour is the same, gets conection, looses conection...
maybe is a hardware issue...

Here's what's added in my /var/log/message when I connect my (working defy) via USB: (USB debugging is not turned on and the USB connection is set to charge only)
May 12 22:33:07 tuxtm kernel: [ 2506.674023] usb 1-4: new high speed USB device using ehci_hcd and address 3
May 12 22:33:07 tuxtm kernel: [ 2506.788858] usb 1-4: New USB device found, idVendor=22b8, idProduct=41d9
May 12 22:33:07 tuxtm kernel: [ 2506.788863] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 12 22:33:07 tuxtm kernel: [ 2506.788866] usb 1-4: Product: MB525
May 12 22:33:07 tuxtm kernel: [ 2506.788869] usb 1-4: Manufacturer: Motorola
May 12 22:33:07 tuxtm kernel: [ 2506.788871] usb 1-4: SerialNumber: <serial_number_here>
May 12 22:33:07 tuxtm kernel: [ 2506.789567] scsi2 : usb-storage 1-4:1.0
May 12 22:33:08 tuxtm kernel: [ 2507.790153] scsi 2:0:0:0: Direct-Access Motorola MB525 0001 PQ: 0 ANSI: 2
May 12 22:33:08 tuxtm kernel: [ 2507.790684] sd 2:0:0:0: Attached scsi generic sg1 type 0
May 12 22:33:08 tuxtm kernel: [ 2507.792748] sd 2:0:0:0: [sdb] Attached SCSI removable disk

with lsusb i get nothing by connecting, if i put the battery in, the next 4sec i get a texas instruments device, then goes off
i guess is hw issue, im trading that brick for a working samsung wave device.
tyvm for the help, but i guess it was a fully brick.

ANSWER!!!
Flash sbf file using rsd lite............IT WORKS........I DID IT...........I THINK U R A NEWBIE

im a newbie, but, rsd cant recognise it, when i plug the phone without battery:
-white led ON
-put the battery (here i can press whatever button, no change)
-white led off
-pc detects new hw (motorola flashing device)
-3seconds
-pc looses conection with motorola flashing device
(even pressing show device at light speed once conected, i doesnt detect anything)
and since on linux i get same result (connect - disconect), it means isnt a pc issue (also tried on another pc)

got an answer for you too
pjgowtham said:
............IT WORKS........I DID IT...........I THINK U R A NEWBIE
Click to expand...
Click to collapse
It's the little "arrow down" key on the left side of your keyboard. Just above the "CTRL" and "arrow up" Key.

hallo.. i'm newbie. i got some proble in my defy
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me
thanks before

omneon said:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
Click to expand...
Click to collapse
you did tap the lower right corner of your screen when android appeared, didn't you?

If right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App

Hardbrick of N7 and hope for help

Hey there,
unfortunately my Nexus 7 2013 Wi-Fi (flo), which was rooted and ran on
Stock Android 4.4.2 and TWRP, suddenly stopped working.
I was experiencing some lags and decided to reboot it, but it never
powered back on. I didn't modify any system files.
I'm unable to enter recovery or download mode, but it seems that it is
now in QDL mode:
lsusb:
Bus 002 Device 017: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL
mode)
dmesg:
usb 2-4: new high-speed USB device number 15 using ehci_hcd
usb 2-4: New USB device found, idVendor=05c6, idProduct=9008
usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-4: Product: QHSUSB_DLOAD
usb 2-4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-4:1.0: Qualcomm USB modem converter detected
usb 2-4: Qualcomm USB modem converter now attached to ttyUSB0
I hope someone is going to be able to help me.

braxas said:
Hey there,
unfortunately my Nexus 7 2013 Wi-Fi (flo), which was rooted and ran on
Stock Android 4.4.2 and TWRP, suddenly stopped working.
I was experiencing some lags and decided to reboot it, but it never
powered back on. I didn't modify any system files.
I'm unable to enter recovery or download mode, but it seems that it is
now in QDL mode:
lsusb:
Bus 002 Device 017: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL
mode)
dmesg:
usb 2-4: new high-speed USB device number 15 using ehci_hcd
usb 2-4: New USB device found, idVendor=05c6, idProduct=9008
usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-4: Product: QHSUSB_DLOAD
usb 2-4: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-4:1.0: Qualcomm USB modem converter detected
usb 2-4: Qualcomm USB modem converter now attached to ttyUSB0
I hope someone is going to be able to help me.
Click to expand...
Click to collapse
Go into TWRP and flash the nandroid you hopefully made for the situation.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
Go into TWRP and flash the nandroid you hopefully made for the situation.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
TWRP doesn' work like i said . I only can get in QDL mode

Have you tried flashing the factory image?
Sent from my Nexus 7 using Tapatalk

i cant get into recovery or downloadmode

braxas said:
i cant get into recovery or downloadmode
Click to expand...
Click to collapse
I suppose you understand or knowleadgeable of getting your phone into Bootloader mode/..
If you can, you can always Fastboot things up..
If you can't, but knew how to, that's a bit scary..

power it off than volume down and power button and after a while it'll show you the bootloader than grab the factory images and flash them onto your nexus. I foyu want more info, search around. I've posted on one of the threads on how to use factory images

https://www.youtube.com/watch?v=XbV5480M5qg
Sent from my LG-MS770 using Tapatalk

I cant use the factory images because i cant get into fastboot or anything else. The only thing i get is the QDL mode.
I cant enter recovery or fastboot or anything else

braxas said:
I cant use the factory images because i cant get into fastboot or anything else. The only thing i get is the QDL mode.
I cant enter recovery or fastboot or anything else
Click to expand...
Click to collapse
I think you're fried, man. Every time one of my devices was stuck in QHSUSB_DLOAD it had to be JTAGed. That's a definite hard brick. Sorry I don't have happier tidings.

RMA is your way. Bad unit. That's what it was
Sent from my Z30 using XDA Premium 4 mobile app

[Q] QHSUSB_DLOAD equals permanent brick?

Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..

frol_swe said:
Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..
Click to expand...
Click to collapse
Have the same problem here

frol_swe said:
Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..
Click to expand...
Click to collapse
Try the nexus 7 toolkit. There are options for recovering bricks. Good luck
Sent from my Nexus 7 using XDA Premium 4 mobile app

[Q] Bricked Find 7

Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version.
http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25
The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made.
Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty?
I can't reach recovery,fastboot or anything
Any help would be much appreciated. Thank's a lot

bcuraman said:
Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version.
http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25
The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made.
Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty?
I can't reach recovery,fastboot or anything
Any help would be much appreciated. Thank's a lot
Click to expand...
Click to collapse
Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006
Let me know if it shows that.
(go to device manager on pc to check that)
If it doesnt show, try taking the battery out and putting it back and then connecting to pc.

suraj.das said:
Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006
Let me know if it shows that.
(go to device manager on pc to check that)
If it doesnt show, try taking the battery out and putting it back and then connecting to pc.
Click to expand...
Click to collapse
yeah: This is the result of the command line:
" 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3)
[50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2)
[50149.664014] wlan0: associated
[51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci
[51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
[51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[51146.928969] usb 1-4: Product: QHSUSB__BULK
[51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
[51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0

bcuraman said:
yeah: This is the result of the command line:
" 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3)
[50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2)
[50149.664014] wlan0: associated
[51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci
[51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
[51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[51146.928969] usb 1-4: Product: QHSUSB__BULK
[51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
[51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
Click to expand...
Click to collapse
Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
Extract it. Connect your phone and then click on the msm 8974download.exe..
Wait till it turns green and then reboot your phone
Thanks to Addel from oppoforums.

suraj.das said:
Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
Extract it. Connect your phone and then click on the msm 8974download.exe..
Wait till it turns green and then reboot your phone
Thanks to Addel from oppoforums.
Click to expand...
Click to collapse
Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?

bcuraman said:
Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?
Click to expand...
Click to collapse
I have no idea. Sorry. Maybe use your friend's pc? OR VM?

Hi there. I too am having issues with my Find 7 as well. I just bought it today. The previous owner apparently went to flash cm11 and he soft bricked it. The phone will power on to the start screen the the screen stays black and goes on and off. I can get to fastboot but not recovery. I have read in the oppo forums that I need to push the stock recovery too it but am unfamiliar with fastboot. I am willing to pay someone to get this phone working. Any input would be greatly appreciated.

MsmDownloader works great from inside an Windows XP VMWare virtual machine.

[Nexus 5X] [LG H790] Bricked device with wrong bootloader

Device: Nexus 5X - LG H790 - 16GB
Hey guys!
I've spent the past... 7hr reading and trying different things but nothing seems to work.
Here's what happened: I was trying to install a custom rom which required a custom bootloader.
Everithing's good 'till I mistankenly flash the bootloader for Nexus 5 instead of 5X. And hell was unleashed... the phone got bricked as soon as I rebooted it.
It won't turn on, no matter the key combination: Power, Vol Up + Power, Vol D + Power, Both Vol + Power, the same while pluggin the USB to the computer, w/ and w/o the power key. It won't turn on.
On linux, the device is displayed as:
Code:
Bus xxx Device yyy: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
And there's only one device generated, a TTY:
Code:
/dev/ttyUSB0
I can't see partitions. If I try to dd the device through the bus:
Code:
:~# dd if=/dev/bus/usb/xxx/yyy of=img
0+1 records in
0+1 records out
50 bytes (50 B) copied, 0.000147159 s, 340 kB/s
:~# xxd img
0000000: 1201 0002 0000 0040 c605 0890 0000 0102 [email protected]
0000010: 0001 0902 2000 0101 0080 0109 0400 0002 .... ...........
0000020: ffff ff00 0705 8102 0002 0007 0501 0200 ................
0000030: 0200 ..
Here's the dmesg output:
Code:
[34405.332730] usb 2-2: new high-speed USB device number 36 using ehci-pci
[34405.465440] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
[34405.465444] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[34405.465446] usb 2-2: Product: QHSUSB__BULK
[34405.465447] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
[34405.465868] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[34405.466518] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
[34425.715761] usb 2-2: USB disconnect, device number 36
[34425.716093] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[34425.716129] qcserial 2-2:1.0: device disconnected
[34430.584072] usb 2-2: new high-speed USB device number 37 using ehci-pci
[34430.716784] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
[34430.716790] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[34430.716792] usb 2-2: Product: QHSUSB__BULK
[34430.716794] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
[34430.717197] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[34430.717303] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
If I connect to the TTY via screen, I always got the same response no matter what (I'm unable to reproduce it right now, but it was a 16 bytes [32 hex chars] fixed response, mostly zeroes).
So, I'm lost here.... the best response I found was to contact LG and ask for a replacement. So, I already sent an email to them. But the fact is, that I live in Argentina, and the phone was bought in USA through a friend, so I don't know if that option is gonna work
Every help is appreciated!
What can/should I do? I use Debian, but I've no problem using Windows 7 x64 if it's needed.

I'm on the same situation. I own a 32gb H790. I was taking random pictures with the google camera app, and suddenly it began to reboot, after that.. endless bootloop. I bought some usb c cables and tried to flash the original images (previous to that, it didn't had any mods, neither root). The flash somehow failed, and it didn't charge or boot since then, it only shows a flashing red light when connected. I couldn't enter recovery nor download mode either so the solution from the other thread didn't work for me. I guess RMA is the only solution for now.
I sent it to LG with a friend (I'm not from USA also), lets see what they say when they see it.

hackancuba said:
Device: Nexus 5X - LG H790 - 16GB
Hey guys!
I've spent the past... 7hr reading and trying different things but nothing seems to work.
Here's what happened: I was trying to install a custom rom which required a custom bootloader.
Everithing's good 'till I mistankenly flash the bootloader for Nexus 5 instead of 5X. And hell was unleashed... the phone got bricked as soon as I rebooted it.
It won't turn on, no matter the key combination: Power, Vol Up + Power, Vol D + Power, Both Vol + Power, the same while pluggin the USB to the computer, w/ and w/o the power key. It won't turn on.
On linux, the device is displayed as:
Code:
Bus xxx Device yyy: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
And there's only one device generated, a TTY:
Code:
/dev/ttyUSB0
I can't see partitions. If I try to dd the device through the bus:
Code:
:~# dd if=/dev/bus/usb/xxx/yyy of=img
0+1 records in
0+1 records out
50 bytes (50 B) copied, 0.000147159 s, 340 kB/s
:~# xxd img
0000000: 1201 0002 0000 0040 c605 0890 0000 0102 [email protected]
0000010: 0001 0902 2000 0101 0080 0109 0400 0002 .... ...........
0000020: ffff ff00 0705 8102 0002 0007 0501 0200 ................
0000030: 0200 ..
Here's the dmesg output:
Code:
[34405.332730] usb 2-2: new high-speed USB device number 36 using ehci-pci
[34405.465440] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
[34405.465444] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[34405.465446] usb 2-2: Product: QHSUSB__BULK
[34405.465447] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
[34405.465868] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[34405.466518] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
[34425.715761] usb 2-2: USB disconnect, device number 36
[34425.716093] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[34425.716129] qcserial 2-2:1.0: device disconnected
[34430.584072] usb 2-2: new high-speed USB device number 37 using ehci-pci
[34430.716784] usb 2-2: New USB device found, idVendor=05c6, idProduct=9008
[34430.716790] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[34430.716792] usb 2-2: Product: QHSUSB__BULK
[34430.716794] usb 2-2: Manufacturer: Qualcomm CDMA Technologies MSM
[34430.717197] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[34430.717303] usb 2-2: Qualcomm USB modem converter now attached to ttyUSB0
If I connect to the TTY via screen, I always got the same response no matter what (I'm unable to reproduce it right now, but it was a 16 bytes [32 hex chars] fixed response, mostly zeroes).
So, I'm lost here.... the best response I found was to contact LG and ask for a replacement. So, I already sent an email to them. But the fact is, that I live in Argentina, and the phone was bought in USA through a friend, so I don't know if that option is gonna work
Every help is appreciated!
What can/should I do? I use Debian, but I've no problem using Windows 7 x64 if it's needed.
Click to expand...
Click to collapse
As far as I know, you are now the owner of a beautiful paperweight. Short of replacing the motherboard, there isn't anything you can do. Hopefully you get a free replacement, but I wouldn't bet on it Best of luck!

Well, thanks guys... I got a reply today from LG, here it is:
Thank you for taking time to contact LG and we really appreciate your e-mail!
I hope everything is going well with you.
You are a valued customer and we regret to hear of any problems you have encountered with our product and we’re very sorry as LG doesn’t expect this to happen. I do recognize the frustration and disappointment this has brought as I would definitely feel the same if this has happened. Please accept our apology for the trouble or inconvenience you have experienced.
In response to your concern, you are welcome to send in the device to our facility so that our licensed technicians may run a full diagnostic test on the device and perform necessary repairs to address the issue - or to have it replaced under warranty if necessary. For your convenience, we will email you prepaid label so you won't have to pay shipping the device back and forth.
I would be more than happy to process a repair authorization for you. Please keep in mind that this process may take approximately 7-9 business days from the day the device is delivered to our facility to the day that it is delivered back to you. If the phone falls under manufacture defect, phone will be repaired right away for free or will be replaced depending on technician’s assessment and diagnosis. You may have an alternate option by visiting your local service provider. Would you like to proceed with the LG service option or would you like to try with your service provider first?
Should you decide to send the unit back, please let us know. Please also include the following so that we can set a repair ticket for the unit:
- phone number
- alternate phone number (if any)
- complete physical address where the unit will be shipped back after repair
- IMEI number (or ESN or MEID number)
- copy of the receipt (bank/credit card statement, email confirmation or order number)
If you have questions or need further assistance, please let me know. You can reach us out via LG Live Chat on our website (link removed, LG's website), or on our phone support by calling our technical support hotline 800-243-0000/ 1-800-793-8896.
Thank you and we wish you all the best.
Sincerely,
Click to expand...
Click to collapse
So, I'm gonna post how it goes, for future reference.

I found someone who fixed a similar brick on another LG phone. I think you can find similar images for the 5X.
I'm not allowed to post links yet so google "hard brick to hell and back"

wbxp99 said:
I found someone who fixed a similar brick on another LG phone. I think you can find similar images for the 5X.
I'm not allowed to post links yet so google "hard brick to hell and back"
Click to expand...
Click to collapse
Yes, I read that one before
No images nor KDZ for 5X
Thanks!

hackancuba said:
Well, thanks guys... I got a reply today from LG, here it is:
So, I'm gonna post how it goes, for future reference.
Click to expand...
Click to collapse
Did you tell them how your phone was bricked? I mean, that you flashed the bootloader for Nexus 5.
I'm in a similar situation (hard brick after "trying" to install original images) and I'm running out of ideas.

I met exactly the very same problem, flashing Nexus 5's bootloader to 5X. Moreover, I'm in the similar situation with you. I live in China and bought 5x in US.
I tried many methods I can find but none of them works. Finally, I send the phone to a local LG Mobile Phone service shop. The staff said the model is never sold in China but they can try. About two weeks later, they told me that, the phone is repaired. I got it yesterday. Until now, it works well.
And yes, they did charge 600 yuan (about 91 usd) from me. Not bad. Wish you have better luck.

guillermo1996 said:
Did you tell them how your phone was bricked? I mean, that you flashed the bootloader for Nexus 5.
I'm in a similar situation (hard brick after "trying" to install original images) and I'm running out of ideas.
Click to expand...
Click to collapse
I didn't actually told them what happened
So far, they told me I need to ship the phone to US and they'll repair it. The only issue now is trying to find the buying receipt from BestBuy, since I don't have it... damn!

Try using the LG UP tool.