Bricked - Blank Screen, No Boot Options, Just Black Screen (no text or graphics)

Well, if there are anyone willing to try what I got I only need one test subject for this. Must be a advance subject in order to test this. Also know that it comes with no promises that it will work. Just FYI Sent from my VS980 4G

is there any possible way that I can acquire or extract the blankflash files or .bin file/the necessary files for the bootloader of the xt926 from another working xt926???

Nobe, sorry for taking so long to get back with this info.  Here are the details I get from my "bricked" XT926M...

Under Windows 7 64-bit (device manager hardware ID details):

USB\VID_05C6&PID_9008&REV_0000

Under Ubuntu 14.04 64-bit (lsusb):

Bus 003 Device 010: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Not entirely surprising, I would expect the phone to show up as the same hardware ID (05C6:9008) on different computers.

The Ubuntu dmesg log:

Please Login or Register to see this Hidden Content

Something interesting here is that the phone first shows up as 05C6:F006, then disconnects and shows back up as the 05C6:9008 QDLoader.  I think this coincides with the green LED on the phone.  I.e., connect it, LED on and it registers as F006, then LED off and it disconnects/reconnects as 9008.  Likely this is entirely normal but I'm curious about the 05C6:F006 hardware ID and going to see what I can find about that.  Could be that is what you see on a SERIOUS brick, one that doesn't even allow the QDLoader to come up, if such is even possible.  (Seems to be an HID device?  Guessing this could just be part of normal USB connection/handshaking routines...)  Note all testing for this post was done using one of the Team Black Hat "factory" adapters.

Seems your previous link and screenshot in post #134 have gone AWOL, or at least I can't get to them. (Entirely possible it is my browser and scripts that I've blocked.)  Hope my info helps you out.  I'm more than happy to look at this as well from the Linux side when the rest of my life isn't in the way.

Now to go and see what has been happening in the XDA thread over the last month...

Nobe, sorry for taking so long to get back with this info. Here are the details I get from my "bricked" XT926M...

Under Windows 7 64-bit (device manager hardware ID details):
USBVID_05C6&PID_9008&REV_0000

Under Ubuntu 14.04 64-bit (lsusb):
Bus 003 Device 010: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

Not entirely surprising, I would expect the phone to show up as the same hardware ID (05C6:9008) on different computers.

The Ubuntu dmesg log:

Please Login or Register to see this Hidden Content

Something interesting here is that the phone first shows up as 05C6:F006, then disconnects and shows back up as the 05C6:9008 QDLoader. I think this coincides with the green LED on the phone. I.e., connect it, LED on and it registers as F006, then LED off and it disconnects/reconnects as 9008. Likely this is entirely normal but I'm curious about the 05C6:F006 hardware ID and going to see what I can find about that. Could be that is what you see on a SERIOUS brick, one that doesn't even allow the QDLoader to come up, if such is even possible. (Seems to be an HID device? Guessing this could just be part of normal USB connection/handshaking routines...) Note all testing for this post was done using one of the Team Black Hat "factory" adapters.

Seems your previous link and screenshot in post #134 have gone AWOL, or at least I can't get to them. (Entirely possible it is my browser and scripts that I've blocked.) Hope my info helps you out. I'm more than happy to look at this as well from the Linux side when the rest of my life isn't in the way.

Now to go and see what has been happening in the XDA thread over the last month...

It switching 05C6:9008 QDLoader means that possibly the battery isn't powerful enough to keep the device in 05C6:F006 mode.

Factory adapter... I think it is actually the reverse.  It is switching to the QDLoader mode once the phone recognizes that it has enough power (or in the case of the factory adapter, has power being provided on pin #4).  QDLoader mode is where I want it for flashing.

Still catching up on the XDA thread... (scroll, scroll, scroll...)

Factory adapter... I think it is actually the reverse. It is switching to the QDLoader mode once the phone recognizes that it has enough power (or in the case of the factory adapter, has power being provided on pin #4). QDLoader mode is where I want it for flashing.

Still catching up on the XDA thread... (scroll, scroll, scroll...)

Which XDA fourm

Since it is easier right now for me to cut/paste between tabs then find the post somewhere earlier in this thread...

Please Login or Register to see this Hidden Content

Yeah, only after I posted the link did I look at your user ID and realized it was familiar.

Please Login or Register to see this Hidden Content

jtag pin xt926

need fuul dump emmc 

Droid hd Source Code file link 

Please Login or Register to see this Hidden Content

I know they posted a fix for the mini and  the X.  I am hoping this file will help with the Droid Hd and Droid Maxx HD

Hey people..

I just note that inside of the only one firmware available for xt925 that we have at the moment (from Canada) has a mbm-ci folder with this blankflash files..

I don't know if this files are for xt925 only or will work on xt926/xt905~907 too.. A friend used to have a bricked xt925 but he sold it as spare part and now we can't test those files..

I hope this helps, obviously use at your own risk
 

Here the link only for that folder:

Please Login or Register to see this Hidden Content

If you want the firmware from canda is here:

Please Login or Register to see this Hidden Content

Edited by Joseberga, 06 March 2015 - 03:17 PM.

May be , it will be helpfu l

Please Login or Register to see this Hidden Content

Any news about this?

Ive got a bricked (green LED) xt925 

Any news about this?

Ive got a bricked (green LED) xt925 

If it shows Qualcomm HS-USB QDLoader 9008 on the fastboot screen there hasn't been. Other wise if your battery is dead you will have to get a factory data cable or a team blackhat adapter that will let you flash with a dead battery.

If it shows Qualcomm HS-USB QDLoader 9008 on the fastboot screen there hasn't been. Other wise if your battery is dead you will have to get a factory data cable or a team blackhat adapter that will let you flash with a dead battery.

For those that are technically inclined, you can make your own factory cable (I would still recommend buying a team black hat adapter, as they're cleaner and more convenient, which is why I bought 3).  All that makes a factory cable or factory adapter the "factory" part is power is being supplied to pin 4 (i think... double check the pin #).

All you need to make a factory cable is any micro usb cable; it does involve soldering, so if you've never soldered before, this is not the project to start on (due to the tiny area you have to work with).  Guides and tutorials can be found via google, and some are cleaner than others.  

If one does so choose to make their own cable, once you've soldered everything, you can recreate the durability of the plastic wire housing with hot glue (I recommend black due to aesthetics; and while not truly relevant, hot glue color delineates the properties of that specific glue).  Place the cable end on wax paper (or a plastic surface) and build up a hot glue layer high enough to cover the solder joints and lock everything in place.  Once done, trim it with a utility knife or razor blade, then repeat on the other side.  You can use a heat gun or the hot glue tip to reheat edges you want smoothed.  Hot glue serves two purposes... first and most importantly, it's an insulator and locks everything in place; secondly, it creates a more aesthetically looking cable end.