Related
I've been running CyanogenMod 10.2 on my rooted HTC One for a good long while now. Since the ROM worked so well, I never had the need to connect the phone to a computer via USB in quite some time. A few months ago, when I attempted to transfer some photos, I ran into a weird and frustrating road block; my phone is simply not being recognized by any computer <see here>
I have updated all drivers
I have enabled debugging in Developer Options
I have tried rebooting Fastboot in bootloader
I have tried using the toolkits
I have tried everything I think I know
The weird part is that the phone charges via USB connected to the computer.
Since it didn't effect much, I just figured it was a glitch and I never ran into a problem again--that is, until today. I hadn't used my MHL adapter with the HTC One (only my GNexus), but after reviewing an intended installation of a Pioneer Appradio, I wanted to ensure that my One would work with the MHL. Hooking up my One to the Samsung MHL adapter (and power supply of course), I get no display on my television.
I am now beginning to wonder if the USB port is damaged. Visual inspection doesn't reveal anything, but I am curious if anyone has had this problem and would appreciate any help. Is there any way to test if I've fouled up the port?
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
cmlusco said:
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
Click to expand...
Click to collapse
No and no
I installed Flashify and did install CWM 6.0.4.7 to see if it would help, but to no avail
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
cmlusco said:
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
Click to expand...
Click to collapse
I have tried adb, but the device never is recognized.
I'm currenty transferring my TWRP backup via WiFi.
I planned on switching to CM11 and see if I can't get it to work after that.
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Subscribed
I'm having the same issue. Stock non rooted and it will not connect. I have tried it on other computers cables ports everything.
Art2Fly said:
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Click to expand...
Click to collapse
You might try a different cord.
Open Device Manager in Windows and then plug the phone in. Do you see it in the list with a little yellow triangle? Do you see Android USB Devices listed?
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
beamer1341 said:
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
Click to expand...
Click to collapse
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Art2Fly said:
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Click to expand...
Click to collapse
Uninstall all HTC drivers and HTC Sync. Then connect the phone. DO NOT choose the option to automatically install any drivers.
Open Device Manager, find the phone. Select the option to manually pick the driver, and select the generic MTP device driver.
This is what worked for me, after countless attempts at re-installing various HTC drivers, different cables and ports, etc.
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Art2Fly said:
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Click to expand...
Click to collapse
Have you tried revoking the USB debugging authorization and then accepting the RSA fingerprint key again when connecting to PC?
Obviously it can't be an USB cable problem if you can connect to it in bootloader mode and use fastboot commands.
To clarify, the phone just charges when connected, it does not detect that it is connected to PC so debugging doesn't even trigger, neither does mtp. I don't even get the slow charging notification
Does it do the same when you plug it in and reboot the computer to "pick up" during boot up process? Or if you run a live CD? I never had an issue like that with my phone but I did have a similar problem with the USB external blu ray drive I bought some time ago. The pc just didn't detect it at all not on any of the ports until I rebooted my PC with the drive already plugged it and for some reason it picked it up. <Not a solution as I don't know what caused it to not be detected in the first place but still...
Not sure if it's an issue with the device(Phone for you, blu ray drive for me) or if it's a problem with the PC even though other things might still work for you as it definitely did for me(phone, headset, mouse, keyboard, usb extender + all the external hard-drives connected to it)...
Problem exists in all computers, Mac, pc, linux
Did you try what I suggest in Post #6 above?
This worked for me when I had the same issue. adb and fastboot would work, but it would not mount MTP.
And just in the last day or 2 I helped someone else with the same issue and fix.
The phone doesn't show up in device manager.
Have you modify the Kernel? (Applying some settings for example)
I browsed over the web for this issue and found some people with the same problems. They solved by removing the settings applied on the kernel or flashing a new one.
I've flashed various kernels and ruu, still same result
Still looking for help
I have 3 of these devices I'd successfully flashed TWRP to months ago. I can plug the other 2 into any of my Win10 PCs and they are functional as MTP devices in TWRP or the OS. Something is wrong with this device in that fastboot works fine, yet it is not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView. I was unsure if this device received an OTA update so I went ahead and flashed the latest stock firmware as of 5/24/2017
It successfully flashed albeit unusually slow (even though Nirsoft USBDevView showed it connected at USB 2.0 and not 1.1). It also successfully flashed the latest Pixel XL Marlin-3.1.0-0RC2
Even if I attempt to toggle MTP in TWRP there is no response in Windows (on any of my PCs) nor is there any response when it's booted to Android 7.1.2. Same when toggled to PTP. Same w/ USB Debugging enabled. The device charges fine. Checking OTA updates shows none available. Factory reset option in bootloader didn't help.
I'm sure I'm missing something like I somehow have the incorrect firmware loaded for something. Anyone know what specifically is responsible for the USB at the firmware level that would allow it to function in fastboot mode yet fail to detect when booted TWRP or OS???
Pay_It_Forward_Pete said:
I have 3 of these devices I'd successfully flashed TWRP to months ago. I can plug the other 2 into any of my Win10 PCs and they are functional as MTP devices in TWRP or the OS. Something is wrong with this device in that fastboot works fine, yet it is not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView. I was unsure if this device received an OTA update so I went ahead and flashed the latest stock firmware as of 5/24/2017
It successfully flashed albeit unusually slow (even though Nirsoft USBDevView showed it connected at USB 2.0 and not 1.1). It also successfully flashed the latest Pixel XL Marlin-3.1.0-0RC2
Even if I attempt to toggle MTP in TWRP there is no response in Windows (on any of my PCs) nor is there any response when it's booted to Android 7.1.2. Same when toggled to PTP. Same w/ USB Debugging enabled. The device charges fine. Checking OTA updates shows none available. Factory reset option in bootloader didn't help.
I'm sure I'm missing something like I somehow have the incorrect firmware loaded for something. Anyone know what specifically is responsible for the USB at the firmware level that would allow it to function in fastboot mode yet fail to detect when booted TWRP or OS???
Click to expand...
Click to collapse
When booted into the OS and plugged into PC, do you have a notification on the pixel that the device is connected and an option to change how to interact with the PC?
TheBobMiller said:
When booted into the OS and plugged into PC, do you have a notification on the pixel that the device is connected and an option to change how to interact with the PC?
Click to expand...
Click to collapse
I can plug it into the PC and charge it up and receive a full charged reached message in the notification bar. Unfortunately I do not receive any other acknowledgement in the notification bar that it's connect to the PC and to toggle from "charge only" to PC MTP connection like most other phones present.
Its not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView.
Yet I can flash it successfully all day long in fastboot mode ... so strange.
Pay_It_Forward_Pete said:
I can plug it into the PC and charge it up and receive a full charged reached message in the notification bar. Unfortunately I do not receive any other acknowledgement in the notification bar that it's connect to the PC and to toggle from "charge only" to PC MTP connection like most other phones present.
Its not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView.
Yet I can flash it successfully all day long in fastboot mode ... so strange.
Click to expand...
Click to collapse
What happens when you change the default USB Configuration in Developer Options to MTP or PTP and the plug in the phone to the computer?
TheBobMiller said:
What happens when you change the default USB Configuration in Developer Options to MTP or PTP and the plug in the phone to the computer?
Click to expand...
Click to collapse
No response on the phone or PC when set to MTP or PTP. Same w/ USB debugging off or enabled.
Pay_It_Forward_Pete said:
No response on the phone or PC when set to MTP or PTP. Same w/ USB debugging off or enabled.
Click to expand...
Click to collapse
I know this may seem like a stupid question, but have you tried using a different cable? If the phone recognizes fastboot mode commands but not PTP or MTP, then perhaps the cable is going bad. I would blame it on your drivers but fastboot mode wouldn't work if the drivers were malfunctioning.
TheBobMiller said:
I know this may seem like a stupid question, but have you tried using a different cable? If the phone recognizes fastboot mode commands but not PTP or MTP, then perhaps the cable is going bad. I would blame it on your drivers but fastboot mode wouldn't work if the drivers were malfunctioning.
Click to expand...
Click to collapse
Same behavior with a different cable. I've also tested on USB 2.0 and USB 3.0 ports. Also different PCs. Up until today I couldn't get Windows to acknowledge anything. Today I observed Windows a couple times present "usb device not recognized. the last usb device you connected to this computer malfunctioned and windows does not recognize it."
However even after it did that once on one PC today and again on another PC today, I couldn't get Windows to present that message any subsequent times. Even when that message did appear as a system tray notification in Windows, Windows still wasn't showing the phone with a yellow exclamation point in device manager like it sometimes can for many other devices it would otherwise present such a message for. (I just speak from past experience with older PCs)
Pay_It_Forward_Pete said:
Same behavior with a different cable. I've also tested on USB 2.0 and USB 3.0 ports. Also different PCs. Up until today I couldn't get Windows to acknowledge anything. Today I observed Windows a couple times present "usb device not recognized. the last usb device you connected to this computer malfunctioned and windows does not recognize it."
However even after it did that once on one PC today and again on another PC today, I couldn't get Windows to present that message any subsequent times. Even when that message did appear as a system tray notification in Windows, Windows still wasn't showing the phone with a yellow exclamation point in device manager like it sometimes can for many other devices it would otherwise present such a message for. (I just speak from past experience with older PCs)
Click to expand...
Click to collapse
Wow...that's puzzling then. You said in your op that you factory reset using bootloader menu but have you tried flashing factory image with fastboot in bootloader? Maybe the firmware that's malfunctioning could be fixed with a factory image flash...
TheBobMiller said:
Wow...that's puzzling then. You said in your op that you factory reset using bootloader menu but have you tried flashing factory image with fastboot in bootloader? Maybe the firmware that's malfunctioning could be fixed with a factory image flash...
Click to expand...
Click to collapse
That's what's killing me. I can successfully factory image flash (same I've flashed on the other handsets). Yet the USB doesn't work in the OS. When this initially happened I thought for sure USB was going to work like usual in TWRP (works on the others) but it doesn't work there either.
The only other thing I can think of out of desperation is flash Pure Nexus ROM or Resurrection remix in the hopes that somehow affects a USB bit setting at the firmware level. (Mind you flashing factory nor TWRP helped).
My exotic theory is that fastboot driver has an ability to work in USB 1 mode and TWRP or OS level driver can only work in USB 2.0/3.0 mode. Even though I don't see any visual defects to the pinout on this handset I'm guessing my pins for charging and for USB 1 mode is fine whereas my pins for USB 2.0/3.0 are electrically damaged or something.
Pay_It_Forward_Pete said:
That's what's killing me. I can successfully factory image flash (same I've flashed on the other handsets). Yet the USB doesn't work in the OS. When this initially happened I thought for sure USB was going to work like usual in TWRP (works on the others) but it doesn't work there either.
The only other thing I can think of out of desperation is flash Pure Nexus ROM or Resurrection remix in the hopes that somehow affects a USB bit setting at the firmware level. (Mind you flashing factory nor TWRP helped).
My exotic theory is that fastboot driver has an ability to work in USB 1 mode and TWRP or OS level driver can only work in USB 2.0/3.0 mode. Even though I don't see any visual defects to the pinout on this handset I'm guessing my pins for charging and for USB 1 mode is fine whereas my pins for USB 2.0/3.0 are electrically damaged or something.
Click to expand...
Click to collapse
Well i guess you could try some ROM flashing and see if that works and if not, try contacting Google and see if they will honor a warranty or something. Good luck to ya!
TheBobMiller said:
Well i guess you could try some ROM flashing and see if that works and if not, try contacting Google and see if they will honor a warranty or something. Good luck to ya!
Click to expand...
Click to collapse
@TheBobMiller I appreciate all your thoughtful suggestions and well wishes. Have an awesome weekend!
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Evnul000 said:
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Click to expand...
Click to collapse
Windows drivers 100%.
null0seven said:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Click to expand...
Click to collapse
I have tried it on both my PC and laptop with both windows 10. Does not work. My PC also has windows 7 still seems to not work. Are there any other drivers i might be missing?
i have also done some research that you should update your drivers from device manager. I dont see anything related to my device. i went to portable devices nothing and i dont have a other devices section in device manager. Any help?
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
null0seven said:
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
Click to expand...
Click to collapse
i am on the latest twrp. will blu-spark help fix it?
ive also found out theres no kedcom driver when i go to fastboot. i even reinstalled adb drivers to insure its there but it does not pop up.
You'll need to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
I once have kind of youre problem connecting to my laptop (win.10). But, at work, on that laptop, connection was ok (win.7).
I reinstal windows 10 and connection works fine, since.
I allways use latest TWRP & version of rom. I can't tell for sure what it's goin on with youre phone.
If i was in youre situation i format my phone (this will erase ALL in youre phone). And if PC still does not see the phone reinstall windows.
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
dentman said:
You'll bed to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
Click to expand...
Click to collapse
What are the driver links if you have? I already installed the OnePlus drivers.
ninjeratu said:
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
Click to expand...
Click to collapse
I used the OnePlus cable and another cable.
Driver issues win 10
Find the excellent tutorial here on drivers.
For some reason my phone didn't show up but was able to receive commands. It was frustrating because I wanted to use the all in one XDA product but couldn't.
Even if you installed drivers they can be broken!
Do drivers from scratch per xda tutorial. Don't forget reboot!
Try different cables and usb ports! My front ones never seem to work!
Don't just try fastboot commands also try adb. Like I said mine wasn't seen properly yet it took the commands.
Unless your windows is a years old install it shouldn't require reinstall.
Factory phone reset might help.
Best of luck!
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.