Related
Hi all -
Thanks for checking in on my tale of woe. The summary is that I have seemingly nuked my partitions on my LG G2 (Verizon Edition VS980) so that nothing happens when I try to power the device on (literally nothing, no logo, no screen backlight turning on, etc.). In Windows, with some coaxing, the device will appear as a QHSUSB_BULK device (with a yellow exclamation point in Device Manager, and even when I boot into Linux to look at the partitions, they aren't visible.
How I got here:
I was happily running XDABBEB VS980 2.3.0 from http://forum.xda-developers.com/showthread.php?t=2715408 with a few Xposed framework tweaks. Great ROM.
I dirty-flashed XDABBEB's VS982.5 v1.0.0 from http://forum.xda-developers.com/verizon-g2/development/xdabbeb-s-vs982-5-v1-0-0-t2975551 to have a look at the G3 interface. I did a Nandroid backup first, like any good crack flasher
I neglected to read the 2nd step of the VS982.5 thread carefully enough - about the fact that this ROM was bumped. I still am not sure what that means.
I played with VS982.5 for a bit, and it didn't really seem like I'd want to use it long term. Also, some of the LG apps didn't seem to work on first try, not sure if that was an additional flash required. (QRemote was what I ran into). Anyway, I thought I'd go back to VS980 2.3.0 for then by just restoring my Nandroid.
Booted into TWRP to restore the Nandroid. It did it's thing.
Upon reboot, the device showed the LG Logo and showed a Security Error in the upper left-hand corner, and sat there briefly, then shut off the screen. (Sorry, I don't remember the precise text, it was in small white letters, several lines' worth of text).
I tried rebooting a couple of different ways, and eventually gave up and followed this guide: http://forum.xda-developers.com/showthread.php?t=2582142
From a Linux Live CD (Specifically an old Hiren's 15.2), I thought I'd followed the instructions correctly. The partitions did show up correctly under /dev/sdk1.../dev/sdk36 or whatever. I did the dd as prescribed with the files.
Then I tried to reboot, and here we are. Apparent hard-brick.
What I've tried since the Linux fiasco.
Rebooting many different ways. (Recovery mode, etc.)
Going back to stock with kdz and tot methods, following this: http://forum.xda-developers.com/showthread.php?t=2432476 . The device is not recognized, probably because the normal USB driver won't load.
Checking to see if it'd show up in adb and fastboot commandline interfaces. No, of course.
Booting back into Linux to try the dd again. No luck. The 30+ partitions don't show up under /dev
Letting it charge, thinking the battery may have died. It has been plugged in long enough that it should be 100%. (I can't tell when the device is on or off any more, because there are literally no indications.). This doesn't seem to have made any difference
Holding the Down button and plugging in the USB port gives the QHSUSB_BULK (Code 28) error in Windows, so at least it's doing something... but not much.
Ideally, of course, I'd like to restore the partitions, get my nandroid written back to the device, and carry on with life. Failing that, I'd like to get the nandroid off so I don't have to spend hours setting up another G2. My mistake for keeping the nandroid on the device - I've never bricked a device this badly, and it's always been recoverable with some googling!
Help!
P.S. Sorry about the cross-post from the General LG G2 Troubleshooting forum - I hadn't realized there was a VS980-specific one.
I had this happen "going back" to a nandroid after testing the new G3 ROM myself...only I was able to boot recovery after the security error...you can't I'm presuming?
I couldn't boot into recovery. But yeah, my device is far past that point now - it seems to be pretty busted.
I'm a newbie that also screwed up his phone after trying xdabbeb's new G3 ROM. Seems like a lot of people doing this. Took a long time, but I was able to get back to stock with the LG Flash tool method. I was able to get into recovery and flash xdabbebs 'restore download mode' file though.
If you don't have recovery or download mode or fastboot screen, I think you are permanently bricked. But I'm a newb, so hopefully some experts will chime in here.
waingro808 said:
I'm a newbie that also screwed up his phone after trying xdabbeb's new G3 ROM. Seems like a lot of people doing this. Took a long time, but I was able to get back to stock with the LG Flash tool method. I was able to get into recovery and flash xdabbebs 'restore download mode' file though.
If you don't have recovery or download mode or fastboot screen, I think you are permanently bricked. But I'm a newb, so hopefully some experts will chime in here.
Click to expand...
Click to collapse
Yeah, my main issue is that I can no longer get my drives to mount in ANY fashion, I just keep getting the QHSUSB_BULK busted driver. in Device manager. I don't know if there is a driver that I can install that'll enable the partitions back in Windows, and I don't know how to install additional USB drivers in Linux.
Mark-7 said:
Yeah, my main issue is that I can no longer get my drives to mount in ANY fashion, I just keep getting the QHSUSB_BULK busted driver. in Device manager. I don't know if there is a driver that I can install that'll enable the partitions back in Windows, and I don't know how to install additional USB drivers in Linux.
Click to expand...
Click to collapse
I would try this. http://forum.xda-developers.com/showthread.php?t=2582142
Sent from my XDABBEB VS982.5 v1.0.0 with ART using XDA free mobile app
z3pp3lin said:
I would try this. http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Thanks - I tried that in my step 7 already, in both Ubuntu and Slax. The dev/sdk1-36 partitions no longer show up.
I thought I'd update this story to let people know how it ended.
I ended up ordering another LG G2, but saw this thread late one night:
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
I had to make a Windows XP VM to get it running with the HS-USB 9008 mode, but after I did that, I kept getting the "device was not found in dload trying flash programmer" error.
I ended up contacting one of the guys in that thread who did a teamviewer session with some custom build of the b2b support tool, and he was able to unbrick it. He does charge for the service though.
It wiped the phone, but it is back in service now under XDABBEB's 2.3.0.
So now I have a spare LG G2 on its way.
I tried installing TWRP but I messed up somewhere, now my screen stays black, when I connect it to the computer it shows this:
oi61.tinypic.com/qqpqg2.jpg
When I try to flash a kdz it stops and it says there's no device connected, I cannot go into download mode or fastboot. When I remove the battery and I keep it plugged in to the PC it shows the battery with a question mark (?).
With the LGMobile Support Tool, when I try to upgrade recovery, it stops at around 35% and it says my battery is too low and it can harm my device if I proceed to update, and it forces me to close it.
Once again, I tried flashing KDZ, I made sure the battery was 100%, I tried to enter download and fastboot mode, no result.
oi59.tinypic.com/15cloq0.jpg
oi61.tinypic.com/qqpqg2.jpg
I can't even format the partition or put anything inside it because it's write protected.
Is there anything I can do to unbrick my phone? (D405n)
EDIT: I have a spare LG L90 if that helps, if I can use anything from that one (software) you could tell me what to try and I'll attempt a fix.
READ A ****ING GENERAL FORUM!!!!!!!!!!!! HEREEEEEEEEEEEEEEE http://forum.xda-developers.com/lg-l90/general/how-to-unbrick-hardbricked-phone-t3100163
TreQUS said:
READ A ****ING GENERAL FORUM!!!!!!!!!!!! HEREEEEEEEEEEEEEEE http://forum.xda-developers.com/lg-l90/general/how-to-unbrick-hardbricked-phone-t3100163
Click to expand...
Click to collapse
No need for the caps and other stuff. I can barely understand that tutorial, if you could fix the grammar and update the steps for better understanding I might be able to do it.
TreQUS: also, the general forum you mention does not yield any help in case you you encounter the "write protected" message. Read better next time.
I will be explaining eeverything that happened. If you don't want to read it and just skip to the information about my phone, then please do so.
Ok, so to start with, I first bricked my phone by trying to unlock my bootloader and flashing TWRP recovery. Luckily I backed up my recovery and kernel images using Flashify, before my first brick. I then followed this to unbrick it http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9. After, I was able to unlock the bootloader and flash TWRP recvoery, following http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690. I used the D405n v20a version of the aboot.bin file and TWRP_2 (I forgot which version). I was trying to unlock the PIE security, because when I used qpyplus 2.7 (python) and typed "python", I got an error. This is my thread http://forum.xda-developers.com/subscription.php?do=viewsubscription&folderid=all. I tried a few times to follow multiple tutorials, which each time, I had to reflash the stock ROM after bricking it, and following the first tutorial I linked to unbrick my phone. I would get an error, saying the version is wrong, or something like that, every time I rebooted my phone. I rooted my phone again, then tried to follow the unlock bootloader and flash TWRP, following this tutorial http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690. Using the same aboot.bin and TWRP.img I used before. It was no longer working. When I went from the very start refollowing this http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9, stupidly I tried reflashing the recovery.img instead of the loader.img. Now, my phone never acts like it did when I was bricking it before. It never shows up in My Computer, doesn't show up in drive manager, showing no partitions, when I go to device manager, under "Other devices", my phone is "QHSUSB_BULK" http://i.imgur.com/QP4fRVp.png. In properties, this is under "general" http://i.imgur.com/CVgbAFR.png. "driver" http://i.imgur.com/38HRDib.png. "details" http://i.imgur.com/ejch5sW.png. "events" http://i.imgur.com/XP3Y3TP.png. I've plugged it into different ports, I commonly have it in COM-3. Upon looking around for "bricked phone QHSUSB_BULK", I found this forum http://androidforums.com/threads/hard-brick-lg-g2-qhsusb_bulk-but-no-partitions-detected.934856/. I scrolled down and saw to install some drivers, so I intsalled them. The phone then came under "Ports (COM & LPT)" as "Qualcomm HS-USB QDLoader 9008 (COM3)".
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
So that is what happened, here is the information on my phone:
LG D405n L90
Android 5.0.2 (Lollipop)
Kernel 3.4.0+
v20a
Stock recovery
Root
Stock Recovery
*I assume most stuff above is reset or different since it's bricked*
Images:
http://i.imgur.com/zTRWMU6.png
http://i.imgur.com/QP4fRVp.png
http://i.imgur.com/CVgbAFR.png
http://i.imgur.com/38HRDib.png
http://i.imgur.com/ejch5sW.png
http://i.imgur.com/XP3Y3TP.png
Attachments:
http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
http://forum.xda-developers.com/subscription.php?do=viewsubscription&folderid=all
http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-flash-custom-t2839690
http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9
http://androidforums.com/threads/hard-brick-lg-g2-qhsusb_bulk-but-no-partitions-detected.934856/
If anybody could help with this, I would be very greatful. Thank you.
If anyone has the same problem above, please follow this tutorial: http://forum.xda-developers.com/lg-l90/general/guide-unbrick-hard-bricked-l90-variants-t3173429 It fixed it for me.
I put Samsung Note 3 ( N9005) Qualcomm based mobile on EDL by ADB Command. The command does work & phone reboot to show in device manager Qualcomm usb Driver, BUT Qualcomm USB drivers disappear after few seconds .... What could be the issue....as i wanted to use QPST ( QFil) to flash the phone but its giving error that no port is selected.
How to make " Qualcomm HS-USB QD loader 9008 " drivers to appear permanently in Device manager.
searched a lot on goolge but nothing is working...
Pls any one help.
When I first purchased this phone I was able to boot to the default recovery that came with the phone ( which clearly had a *fastboot option*), it came with stock 5.1, and a bunch of bloatware.
I downloaded the one click root method for the h811 which was perhaps the easiest root i've ever done. great. i also had to flash my recovery to twrp 2.8 for some reason.
Rocked out to a newely rooted device on 5.1 until the t mobile bloatware and system update notification kept bugging me, so I said * eff it, i've been holding out for a while*
So I get to the cm 13 wiki for my device, I managed to install the cm recovery ( cant remember how i did this for some reason) and then i was able to flash cm13 to my phone. CM13 is sleek, and smooth but is presenting problems.
First of all, no google play store and the gapps zip wont install through cm recovery ( fails and tells me to use twrp instead which is a problem because i can't boot this phone into fastboot mode)
I am unrooted and can not figure out how to properly root a T mobile h811 running cm13, so the twrp manager doesn't work because it "requires root" then shuts down. ( enable root access in the cm13 developer options does nothing at all and yes, for adb and apps)
FAST BOOT MODE DOES NOT SEEM TO EXIST ANYMORE ON MY PHONE - Following the many tutorials, which goes long the lines of using adb/fastboot, adb devices can see my device, but fastboot devices can't ( figures) because its not in fastboot mode. Any fast boot reboot bootloader or any variant of that command only reboots the phone, to... swipe the screen.
I've installed the lg bridge crap ( which installed an updated usb driver) that doesn't even recognize my phone " no mobile device connected". tried uninstalling and reinstalling, but nothing. When putting the phone in download mode, to see if adb would rcognize it, windows sees this as a new device , installs drivers but says " device can not start, code 10 * in device manager. :silly:
is there anything that can be done?? google searches result in obvious solutions that SHOULD work but don't, or threads where a person coincidentally has the same exact problem as I do, but their response is usually the last response in the thread that goes unanswered
summary : I've install cm13 on my lg g4 h811, I do not have root access, I can not install twrp due to ( no fastboot mode) in effect, i cant install gapps, cant root phone etc..
any help?
did you ever unlock the phone....?
Yes, unlocking the phone is one of the first things you would need to do. In Developer Options > OEM Unlock. Then in bootloader, run the unlock command. This will delete /data and internal storage so back up your files so you can transfer them back via adb or fastboot.
Then you're probably going to need to temp boot TWRP, then flash the TWRP recovery image in TWRP. THEN you can flash properly.
Carefully read through this thread:
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Good luck.
Edit: oh and this thread belongs in Q&A.
Alright. Am I only to read the first post or all 30+ pages? ( not that i have a problem, just curious)
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
aoaleman said:
Reeeeaaadd ittt alllll! Just kidding. The first post should be fine. You'll be looking at doing everything after flashing the kdz. If you think you've messed up your partitions, flash the kdz and start over.
Click to expand...
Click to collapse
"ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it."
didn't work, very frustrating. any clues? on windows 8.1 by the way. tried two computers. none can see this phone. I can connect the phone to the computer and see its storage, lg usb driver is installed
You probably need to reinstall the drivers. It might be the fastboot driver. That's what worked for me.
I've reinstalled the official drivers, uninstalled them... Jusst the mobile USB driver, a combo of both, plenty of times. Don't understand why this software doesn't see my phone
Lgup, lgair, lg bridge, lg USB driver (skinned down) .. Nothing works tested on my gaming rig., and work laptop both running win 8.1 64 bit
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
TacoTuco said:
Hey man next time you have a question just post it in the Q&A section this section is forces android development just wanted to let you know
Click to expand...
Click to collapse
This section does get more views though haha.
Anyway I feel that the 811 is one of the more finicky devices to get into fastboot at least in my experience. I had to enable and disable dev options while plugging and unplugging device and it finally worked. No idea if that'll work for everyone though.
I reasked the question in Q and A. Please help some one.
You start over. LG bridge.
Having the same issue. I'm on Windows 10. What developer settings did you mess with to get it working, tiskewlio?
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Sunaj1 said:
The issue i seem to be having is that when I put the device in download mode ( didnt know that is the same as fastboot) drivers attempt to install, "LGE MTP USB DEVICE" has a yellow exclamation mark with a code 10-device cannot start error message. I believe this the issue as any fastboot command stuff says " waiting for any device" . must not yet see the mtp driver .. Also noticed the bridge app immeditaley tries to pick up my device in download mode but fails due to this problem..
Any clues?
Click to expand...
Click to collapse
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
thevirgonian said:
]
Make sure you are using all these files...
https://drive.google.com/folderview?id=0B_sPus48oLWYQy1MTFRBSlBxMGc&usp=sharing
Click to expand...
Click to collapse
silly question maybe, but is there a specific tutorial in getting this to work with the files provided given my situation? (commands, etc..) will this somehow bypass the the lge mobile mtp device that wont install ? I had installed the system wide adb/fastboot drivers, and already had a folder with just the minimal install of the adb but didnt have a few files in the one you provided ( lg root, busy box, etc) so not quite sure what to do with them.
Again, if possible want to flash twrp recovery to my device but can't due to * waiting for any device* and the ( device cannot start ) error
Thanks
* waiting for device* when putting phone in download mode and pushing fastboot flash twrp-2.8.7.1-h811.img.
Any help would be appreciated as I need to get the driver to work first. see attached picture.
Cha h
the issue is largly resolved as i've been able to flash the recovery and install another rom. But i'd still like to know how to get the download mode driver properly working in the event i need a computer and can't do a self contained install.
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
travisd4est said:
Uninstall all drivers. Reboot computer. Reinstall latest drivers and LG bridge. Reboot. Then start your process. It'll work. Trust me. Find my posts in primes stock thread. I ran into this issue myself. And if you get an error after flashing where it won't mount /data, that's because it got corrupted. Once in twrp, format /data then reboot to recovery. All will be well to flash. Just a heads up since that was also a problem.
Click to expand...
Click to collapse
i dont know man, i did all that a million times over, but recently i was able to just flash the stock MM rom to the device using LGup. Think i'll just stick with stock rom and root for a while as all this stuff is a little finicky at times. Thanks for your help.
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk