Develop Bugs

Hard Bricked LG E980 USB device not recognised

My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:

Have you installed the LG drivers for your pc and tried the unbrick method?

Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660

There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .

twill1987 said:
My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Click to expand...
Click to collapse
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app

Yes
riki126 said:
Have you installed the LG drivers for your pc and tried the unbrick method?
Click to expand...
Click to collapse
Yes I tried that. The drivers won't install. I even used another windows 8 computer my roommate has and switched out
the usb cables, still came back "unknown device"

shabbypenguin said:
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
Click to expand...
Click to collapse
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.

Okay
stulzerl said:
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"

twill1987 said:
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
Click to expand...
Click to collapse
I've had similar issues when i had my optimus g. I had to use a pc with xp to flasht he phone, dunno why though. You could give that a shot.

twill1987 said:
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Click to expand...
Click to collapse
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .

Thanks
WeActOnImpulse said:
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
Click to expand...
Click to collapse
I have tried this and unfortunately since the USB drivers aren't detected by the computer there is no way for me to flash back to stock.
Thanks for the information though, I appreciate it.

shabbypenguin said:
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Click to expand...
Click to collapse
Wow, that sounds awesome. I followed most of that. I access download mode on the device by pressing vol up and down simultaneously and plugging in the usb cable. I am more willing to try this, and if it works I will pay you from my paypal. I guess all I need now are those files to run to the sd card. I read the tutorial you posted for the samsung and downloaded the windows disk manager. I am eager to try this method, though it is admittedly very new to me.. If you can post those files, I will follow the instructions you give and pay you a little bit of money for your help!
I am a broke college student so it won't be much, but I really appreciate your response and information on this method with the qualcomm s4.

Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0

Just wrote it to sd card
shabbypenguin said:
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Click to expand...
Click to collapse
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.

twill1987 said:
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
Click to expand...
Click to collapse
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.

Possible hope??
shabbypenguin said:
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Click to expand...
Click to collapse
I meant I used the windows tool to write the debrick.img to the sd card. But no dice, the device isn't recognised.
However! I installed a driver clean up tool and now if I plug in the device it is recognized as Android Original ADB Interface.
The LG Flashtools even says the port is ready! But I get the error code "10" "device cannot start, A request for the USB device descriptor failed."
So now I am stuck on that instead lol. This just sucks.

that sucks about the sdcard, it must be because you arent "truly" bricked. sorry i thought it would help ya :/.

What is the driver repair tool you used? I know this thread is old but I'm having the same problem. I was trying to root my E980 and now my computer wont recognize my device. The phone works perfect, its just when I plug it in to the computer it isnt recognized. How can I fix this?

+1
Just wondering if anyone's come across a solution to this besides a sledge hammer... been having the same "Code 10: Device failed to start" when in Download Mode, though Windows finds a driver fine when the phone is stuck on the LG screen... doesn't help much, though, 'cause it won't receive adb commands. I manually installed the LG USB Composite Device driver, which added a modem and a COM port, both of which Windows recognized to be active, but the LG FlashTool USB Viewer showed no open pipes. I'm a relative noob, so please feel free to point out the obvious, like an alternative to adb that the phone can always receive or a way to brick it the rest of the way so the MicroSD trick will work.

I came across this problem like the OP and just wanna let everyone know that you have to use computer with USB 2.0 port then the driver issue would be fixed.

[Q] Wiped everything with TWRP 2.8.4.0, now softbricked?

So just as the title says, but here's a little back story (might help).
I'm trying to help out a friend with his Bell Mobility i747M. He wanted to try out Lollipop, so I looked into it and said I could do it. Last I even touched his phone was quite a while ago when he wanted me to flash CM11, back when KK was still pretty new. So it's been over a year. I flashed CWM back then, got the ROM installed, and everything has been good ever since. Fast forward to now, and he wants to try Lollipop. I figured the first thing I should do is update the bootloader/radio, which went perfectly fine (after some researching, I chose 4.3/MK5 for his i747M). I tested them by booting back to the ROM and checking About Phone - everything was good. So I booted back to the old version of CWM, and thought it would be a good idea to get a more modern recovery. CWM or TWRP didn't matter, just as long as it was more up to date (I thought it might help with Lollipop compatibility). So I decided on TWRP, and I got the latest version (2.8.4.0 as of now) and flashed it. Successfully flashed, then rebooted recovery. TWRP is there and working. Great. Next step... I had the Lollipop ROM and Gapps already downloaded and ready to go, so in TWRP, I proceeded to wipe everything (system, data, cache, internal sd).
Uh oh... Half way through wiping, the phone reboots itself! Now there's no ROM, so naturally it has nothing to boot to. Try going back to TWRP, and I see the splash screen again. OK, false alarm... Well, not really... Because now it just reboots itself after the splash screen, every time. Can't get into TWRP no matter what! I can access download mode, but Odin doesn't recognize the phone. Yes, I have the drivers. In fact, the device isn't detected by Windows at all.
So here we are. Download mode boots, but Odin doesn't work because there's no communication through USB at all. There's no ROM on the phone because it was wiped. And TWRP won't boot beyond the splash screen.... Now what?? I tried the 80MB MK5 debricking .img on a 64GB microSD. It does nothing - besides, USB isn't reading anyway, so it's not like I can proceed with Odin.
I'm at a stalemate here... Any suggestions?
My friend's gonna kill me if I killed his phone I'm pretty experienced with several devices, but not much with Samsung. I've never seen anything like this happen before...

When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?

audit13 said:
When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?
Click to expand...
Click to collapse
Yeah, I figured that would be the case. Just about done downloading Ubuntu which I'll boot from USB. I'll post back with results once that's ready. I should have it booted within 10 minutes. Once I get there and verify the phone connects, what would be my next step? Should I try flashing stock 4.3 first?

I would confirm the bootloader that is on the phone before flashing anything from sammobile.com.
You may be able to use fastboot commands to get the information by typing fastboot getvar all.

OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.

Bloodflame said:
OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.
Click to expand...
Click to collapse
No luck. wrote to the SD successfully, and it just boots to download mode. Nothing else.
ADB and fastboot still do nothing

Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?

audit13 said:
Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?
Click to expand...
Click to collapse
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Edit: Downloading Heimdall (Linux-compatible Odin)...

Bloodflame said:
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Click to expand...
Click to collapse
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?

audit13 said:
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?
Click to expand...
Click to collapse
Plugging into the wall makes the phone vibrate every couple of seconds, but nothing shows up on screen, and there's no indicator light.
The vibrations lead me to believe it's detecting something, but no indicator light worries me (unless that's just because there's no kernel)
The red light does come on if I plug it in without the battery.
Heimdall fails to detect the device as well (no surprise there)

If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.

audit13 said:
If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.
Click to expand...
Click to collapse
I agree that it is weird, because it's not coming up as a device at all, in either Windows or Linux, yet it does receive power.

I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?

audit13 said:
I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?
Click to expand...
Click to collapse
The debrick image is what I've been trying. It's on a 64GB microSD. And I made a new one from Linux a few minutes ago (booted back to Windows now).
The battery was about 80% before all this started, and the phone powers on without being plugged in, so I doubt it's the battery.

Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.

audit13 said:
Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.
Click to expand...
Click to collapse
I only have one card over 16gb...
Either way, I still have the USB problem. I'll need USB to flash with Odin. The debrick card only seems useful when Download mode isn't working, but that part works fine on the phone, even without the debrick card. My problem is with recovery. If I could run that from the SD, I think I would be fine - just flash a ROM. But I'm not finding anything for that (not surprised).
I thought it could potentially be a corrupt driver, so I tried using USBDeview to uninstall all disconnected devices. I tested it with a portable hard drive, which indeed had to reinstall after. So the program works as intended. However, the phone still isn't detected when I plug it in. No sound, no notification saying it's installing or install failed - absolutely nothing. Power goes to the phone through USB, with multiple cables and USB ports. Just no data connection.
I'm starting to think there's just nothing I can do...

The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.

audit13 said:
The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.
Click to expand...
Click to collapse
Yeah, that's what I'm thinking. Found this, and it's cheap enough... But that shipping!

You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill

audit13 said:
You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill
Click to expand...
Click to collapse
Yeah, doesn't look easy. I already tore down to here, and visibily, it looks OK. I'm not so sure about soldering either :silly:
I appreciate your assistance.

Can't get the phone to recognize data connection through USB port

Sadly i had to come to the painful conclusion that my problem relies at this point on the data detection of the phone itself.
I have read tons of tutorials pointing to adb or fastboot upgrades and different stuff and methods to update. I'm stuck in 2.20.40.139 and cannot find an update within the OS. I will enumerate now the things i see in order to clarify this situation.
_USB debugging on or off makes no difference.
_MTP or the other mode returns nothing. No detection on device manger in windows.
_Phone always charges when plugged to USB ports.
_Tried 4 cables and 3 pc's all of them tested with other phones and tablets.
_On fastboot mode nothing happens and device is nowhere to be found.
_ADB is the same. adb devices shows nothing for this.
_Recovery returns an error as if it tries to update something that isn't there MOFD_SUPDATE.zip
_after that error i get into recovery pressing power+vol up for a few seconds.
_did a factory reset on the phone and wipes in recovery.
_copied file in root of the phone. Detected the update. failed when trying to apply.
_bootloader in fastboot shows unknown. serial is 0123456789ABCDEF or something like that (serial was ok before i used the bootloader unlocker from ASUS website)
i can't think anything else for this right now... it's really driving me crazy since android works without an issue. Phone is not rooted or even has been tried to root.
If someone knows or can think anything regarding this please help me out. There's nothing i like more to share thoughts and ideas to have this updated.
Thanks in advance,

see thread about unbrick soft/hard bricked zf2

I Guess I Discovered a New Form of Hard Bricking on my Device???

I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.

jasonstackhouse said:
I was running the Developer Preview Beta 2 and noticed that my device would no longer communicate correctly with my OTG usb jump drive, I tried all the normal trouble shooting techniques and nothing worked. I than tried connecting my phone to my computer and my computer would no longer connect to my device either. I didn’t think this was a big deal so I was going to just flash back to the May factory image from my computer.
This did not work, so I did a factory reset in TWRP hoping that this would clear out the issue that was stopping the phone from usb communication. It did not fix the issue. So normally in TWRP I can always plug a flash drive into the phone through the otg and explore the files, however for some reason this was still not possible, something has happened to the device where it no longer allows incoming or outgoing usb communication. The device still charges however it is no longer recognized at all by my computer nor does the device recognize usb drives. I have all the latest USB drivers and updates needed. I uninstalled and reinstalled my drivers on my computer as well. The main issue I feel like I am having here, is that the device no longer wants to communicate with usb asides from charging, this is why it is not seeing the otg storage when I plug it in while I am in TWRP.
I am at a loss, I can boot into twrp and explore the device, this is useless as i deleted all the files on the device, TWRP will not allow a usb to be found so i cannot flash anything to the device. My computer does not see the phone so i cannot fastboot anything to the device. I have tried everything, DUECS script, skipsoft, none of them have identified a device. This is further verified by running cmd and typing in adb devices, to which the response is a blank line.
How can a device be bricked, but somehow have TWRP recovery working, along with the ability to boot the device into fastboot/the bootloader (and yes the bootloader is unlocked still)? If anyone has any ideas of how I can get this thing to be recognized by my computer please let me know.
Click to expand...
Click to collapse
I would try a different cable as this device is very finicky; that solved my issue of the computer not recognizing the phone.

Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?

Az Biker said:
Is it possible that your device's USB port data transfer function is damaged, but the charging portion is functional, making it a weird hardware failure?
You know, like the old days when the charge port would break or wiggle loose, and sometimes it would charge and sometimes it wouldn't, depending on the angle of the cable in the mini usb port?
Click to expand...
Click to collapse
That would be nice if that were the problem, but unfortunalty I do not think it is. For example, when the issues first began, before I did the factory reset on the device, windows would pop up a message that said unknown device, and failure to connect. After the factory reset in TWRP the computer gave up all together in recognizing the phone. Another sign it was likely not a hardware failure was when the device was on and i was attempting to connect the otg usb to the phone it would give me some weird options. With android P the options were, allow this device to control the usb, or allow the USB to control the USB. that made no sense to me since why would i want the the USB to have any control, it couldnt do anything its not a computer its only a storage device. However, even though I had file transfer selected in developer options, it would not allow this connection. The options were all greyed out and it would not allow the pixel to have control over the usb device.
As for USB cords I have used without fail the google issued USB cord that came with the Pixel 1 xl, It has never faile me or had any issues. It is still fully functional as I was able to use it to connect my girls note 8 to my computer for file transfers and all other things my phone is not doing anymore.
I reached out to google and explained the situation to them, after i told them I was on Dev preview beta and they verified this to be true they told me this is likely a hardware failure and offered to replace the device. I am now waiting on the new device to be sent to me, however still cant accept that i cant recover the current device with an unlocked bootloader, TWRP installed, and access to fastboot/bootloader screen. I have seriously bricked phones before as in they would not even turn on and I was able to get them back up and running, this would be my first ever device I could not recover and what makes it worse is that it actually has TWRP installed and powers on and off just fine.

Sorry for the obvious question: Do you have the latest drivers? I don't have the drivers set to the whole system (Windows), so if I don't CD into my fastboot folder, I can't do anything because the system wide drivers aren't current. Don't know if that could be your issue?
I'm too lazy to fix the PATH of my drivers ¯\_(ツ)_/¯

I had an issue similar to this. I was trying to hook up a USB c to Ethernet adapter. It worked fine on April's patch but after I flashed Mays the phone wouldn't recognize it. After I plugged it in my phone rebooted and I no longer had access to developer options and it wouldn't read any usb device. Luckily I had a TWRP backup on my device. Once I flashed the backup which was only about a week old everything worked again. I haven't tried using the adapter again. I think something in the data partition got corrupted. I tried just restoring the boot and system partition and that didn't fix it. Try doing an advance wipe and formatting the data partition. That might get you back up and going.

have we even seen a bricked device yet?

twiz0r said:
have we even seen a bricked device yet?
Click to expand...
Click to collapse
I didn't think it was possible, I still dont understand how this is happening. For the other responses above, I have all the drivers up to date, and I already formatted data, wiped everything. At this point I would like to see if there is anyway to delete TWRP recovery from the device, anything, I have no OS on the device, but for some reason still have TWRP on both A and B.
I almost dont want to give the phone back to Google because I want to figure out what happened and how to fix it, its definitely not broken/bricked like you see when someone flashes the wrong files to a device, it just has no USB connection capabilities which in-turn have rendered the device useless.
When I had Samsung phones if you bricked a device to the point it doesn't even turn on correctly you could always save it still using ODIN. Its weird that the google flagship device and software doesn't have its own proprietary flash software like Samsung, LG and HTC, we just have adb/fastboot, I feel like if we did, i may be able to get this thing started again.

have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image

Pyr0x64 said:
have you tried using something like quickboot from the playstore to be able to get to fastboot?
I had a similar thing happen a few weeks ago on oreo. PC wouldn't 'see' the phone, but it would charge very slowly.
I installed quickboot, booted to fastboot and was able to flash the factory image
Click to expand...
Click to collapse
I can't access the play store on the device in it's state. I do have access to fastboot. I can boot the phone to fastboot, and into TWRP, only problem is the phone doesn't communicate with the computer in either state. If the pixel had a SD card slot I would just load up a recovery but unfortunately we don't have that luxury

What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs

Triscuit said:
What cable are you using to connect to the PC? Is it USB c to USB c?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
The cable is not the issue, I confirmed this by testing all my cables with the new device that I just received for my warranty exchange. I also tried my luck with Linux, after a complicated installation on my computer I was able to have Linux actually detect the device (partially) when the device was plugged in at splash screen I got nothing, at fastboot/bootloader screen nothing, but once the phone booted into TWRP it came up as AOSP device, when I attempted clicking on the AOSP device being detected by Linux an error message popped up telling me mtp or midi error, not sure for sure what one it said. Either way I couldn't connect for any transfer of information, I tried adb sideload and that failed as well.
This has been an experience for the memory books, glad that old device is gone and I'm back up and running on a working phone. No more beta testing for me, I'll be ready for Android P when they get it out of beta, I don't have the time or patience to deal with any more warranty exchanges.

Unable to see Nexus 7 in fastboot mode

I may have royally mucked up my Nexus 7, but I am hoping there will be a way to rescue this.
Basically, a bit of knowledge that I thought meant I could get out of everything has probably led to me being a bit too careless with what I was trying, and I have done a great many stupid things with the tablet today.
I can get the Nexus into fastboot mode, but apart from that, all it will do is sit on the Google logo. I believe I have wiped the OS and although I had TWRP, I think I may have wiped this too.
I cannot get my Windows 10 laptop to recognise the Nexus when I plug it in - possibly due to poor attempts to update drivers. "fastboot devices" lists nothing, and I cannot see an entry for Android devices in Device Manager. I have read that a Windows computer will not detect an unknown device if it is plugged in while in fastboot mode, is this correct?
Does anyone have any suggestions as to how I might manage to get any sort of ROM onto my tablet that may allow me to reflash it and get it working?
(Data recovery is not a concern - at least I did that before I started playing)
Thanks

kitiara2016 said:
I may have royally mucked up my Nexus 7, but I am hoping there will be a way to rescue this. Basically, a bit of knowledge that I thought meant I could get out of everything has probably led to me being a bit too careless with what I was trying, and I have done a great many stupid things with the tablet today. I can get the Nexus into fastboot mode, but apart from that, all it will do is sit on the Google logo. I believe I have wiped the OS and although I had TWRP, I think I may have wiped this too. I cannot get my Windows 10 laptop to recognise the Nexus when I plug it in - possibly due to poor attempts to update drivers. "fastboot devices" lists nothing, and I cannot see an entry for Android devices in Device Manager. I have read that a Windows computer will not detect an unknown device if it is plugged in while in fastboot mode, is this correct? Does anyone have any suggestions as to how I might manage to get any sort of ROM onto my tablet that may allow me to reflash it and get it working? (Data recovery is not a concern - at least I did that before I started playing) Thanks
Click to expand...
Click to collapse
Have a look at this thread. Check if this app detects it.

UsbTreeView does detect it (yay) and it is now showing in device manager and fastboot devices lists it.
Hopefully now I will be able to "talk" to the nexus and get twrp/ROM back installed - at least there is a glimmer of hope.
Thanks