Develop Bugs

[Q] Nexus stuck in boot loop. how get to install drivers?

Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!

dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.

First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?

dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.

cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?

dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.

Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium

WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.

Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium

ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.

dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!

bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......

Anything at all? Anyone?
Sent from my Nexus 4 using xda premium

dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.

bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?

dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.

bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.

Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.

rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...

[Q] Can my N7(2013) still be saved?

Hi, my N7 is bricked and I wanted to fix it.
I tried to flash ROM but couldn't do it since my computer wont recognize my N7 (except in Recovery Mode-> Sideload).
I think it has something to do with the "developer options -> need to check USB Debugging", however, I can't do that since my phone when turned on, Google Logo appears, then afterwards, BLACK SCREEN (and now in a loop, but there is no X logo just plain black).
My phone is rooted & unlocked. Out of curiousity (My fault), I bricked my N7.
I've read a lot of article on how to unbrick my N7 and I think I now know how to do it- through Android SDK/ADB Tool. I've also read the a guide on how to change drivers (and tried it in all possible ways I can think of), and it did install the driver. However searching my N7 through ADB Tool doesn't go through.
adb devices
List of devices attached
(**nothing follows**)
But if I turn my N7 to Recovery Mode->apply update from adb:
will show the result:
adb devices
List of devices attached
**serial number** sideload
I don't know what other ways in order to unbrick my N7.
I hope you can help me with it.

You can enter bootloader, right? Then try to use fastboot to flash a new rom.

Use wugs program but tick tablet is in bootloop.

Can you boot a brick in to recovery mode? No...so you aren't bricked...

Thanks for the info man!
AnarchoXen said:
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Click to expand...
Click to collapse
Hi, thanks for the info... I already solved my problem.. If only I have read your post earlier I could've saved xx hours in my research!! LOL
donb1 said:
Use wugs program but tick tablet is in bootloop.
Click to expand...
Click to collapse
I tried, but N7 isn't recognized by PC. So the main problem is really how to make my N7 recognized by PC (ADB/bootloader).
But problem fixed now. Thanks!
Calvin Gross said:
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Click to expand...
Click to collapse
Before I fixed my N7, this is what I tried. But the problem is, PC wont recognize/find my N7 when I do:
adb devices nor fastboot devices
But, I already fixed my problem. Thanks for the response! Greatly appreciate it!

Nexus 5X hard bricked, stuck in QHSUSB_BULK

Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).

oscillik said:
Last night, whilst trying to flash all the phones in our house with their respective Nexus factory images, I inadvertently ended up running the flash-all.bat for a Nexus 5 (hammerhead) onto a Nexus 5X (bullhead) by mistake. It got as far as flashing the radio and bootloader, and rebooted the phone.
And now the phone won't turn on at all.
Can't get into fastboot mode with key combination (I'm assuming because the bootloader for the Nexus 5 was flashed mistakenly).
When plugged into a computer, it shows up in Windows Device Manager as QHSUSB_BULK.
ADB and FASTBOOT won't see the phone at all.
Can anyone help? I've tried looking online for this but the only hits I'm getting are specifically for other phones, not the Nexus 5X. A lot of the steps to resolve seem to be extremely specific to those phones (i.e. - there's a thread here about the Nexus 5 but the restore file is only for the Nexus 5).
Click to expand...
Click to collapse
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?

alvinhochun said:
Well, that happens when you flashed the wrong bootloader image.
I remember reading about there being multiple modes with QHSUSB_BULK? Some seems to require images signed with keys from Qualcomm...
Can you take a screenshot in Windows device manager? Also try getting the USB VID and PID if possible?
Click to expand...
Click to collapse
Yeah, this is likely going to be an expensive lesson in making sure I don't have multiple factory image folders sitting on my drive, ready for flashing onto the various Nexus phones I have to 'administer' for my family and friends!
From what I've been able to gather, I had already come to the conclusion that it may be salvageable, providing I can get access to the appropriate partition image files from Qualcomm and the appropriate tool to flash it, and instructions! I've seen as much for the Nexus 5, but nothing for the Nexus 5X.
I can try and get some screenshots later tonight, and even boot up a Linux box to get some more info.

Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...

alvinhochun said:
Perhaps there is an easier way...
There should be a "backup" bootloader partition (in fact, I just checked my 5X and there is one).
Perhaps try holding all buttons to get it to use the backup bootloader? But first you need to get out of the QHSUSB_BULK mode.
Reference thread for N5: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
And then if you managed to boot the backup bootloader you should be able to just use fastboot to flash the bootloader again.
Edit: Now that I think about it, it may be bricked on even earlier boot stages since I think the bootloader image contains them as well. Probably still worth a try but I guess your chances are pretty low...
Click to expand...
Click to collapse
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!

oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.

alvinhochun said:
What if you hold the power button for a few seconds? Like more than 10 seconds? I think it should reboot the phone.
Click to expand...
Click to collapse
If it reboots the phone, I'm not getting any feedback from the device whatsoever of that happening. Nothing appears on the screen, no vibration, no sound. Even if I do that while it's plugged into the computer, I don't get the Windows 'disconnect / reconnect' USB device sound (if you get what I mean?) to denote that a device has been unplugged/replugged back in - which is what I would expect to happen if I power cycled the phone whilst it's connected to the computer.

Hi,
I am dealing with the EXACT same situation. Did you find any solution to this? I wanted to sell my 5X in order to purchase 6P and when the buyer came I wanted to un-root the phone and write back the original recovery image. Anyway, I ended writing the bootloader also, but from my wife's Nexus 5 (hammerhead) and not from 5X

Same problem. Tried a lot of qualcomm tools and the lg flash tool with tot file. Doesnt work.

bricked
Hey brother, I am sorry to say you are screwed. I just did the same thing to my phone two weeks ago. It seems without the bootloader the phone will not react at all and yes the flash-all script flashs bootloader first then restarts but once the nexus 5 bootlader is flashed the phone cant start the bootloader.
here is my thread i started with some responses but its all bad news
http://forum.xda-developers.com/nexus-5x/help/hard-bricked-phone-t3278033
There is a plus side for you that is not for me. I have called google and was 100% honest with them as to what happend. They told me they would not warranty me out a new phone since its my fault. However they did say because it is a software issue LG should be able to fix the issue. I already started the RMA process and my phone should be arrivng at LG on monday (two days from now) so hopefully they cover it under warranty or charge me something small to just flash the proper bootloader.
I will report back to my orignal thread and this one for others as I am betting as time passes a lot of original nexus 5 owners who upgrade and are used to flashing a lot will also make the same careless mistake.

Great news!! LG has repaired my phone and said they sent it back to me today. I have not confirmed it to be working as its in the mail but was told the phone has been repaired. So all you guys that do this while still under factory warranty can have your phone repaired by LG direct. Don't bother with google they can't repair it.

That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.

anjelika said:
That's great news! I wonder if the repairing was done by changing the motherboard or they've been able to re-write the eMMC chip. Anyway, take good care of it
P.S. Did you told them that you wrongfully wrote the firmware from another phone or they didn't asked? I wonder if this could be considered that you void your warranty or not.
Click to expand...
Click to collapse
They told the truth and everything worked in their favor: http://forum.xda-developers.com/showthread.php?t=3278033
Sent from my Nexus 5X using Tapatalk

the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -

konsolen said:
the bulk mode is the qhusb 9008 mode. With the right files a unbrick is possible. Unbricked my G3 also from 9008 last week.
But the prob is to get the right files.
I get the files for the flex2. So iam try if i could rewrite those files.
I dont want to send it to lg, its funny so solve it with my own hands -
Click to expand...
Click to collapse
pardon me , did you have solve it ? my 5x have this problem for a week , i can't find the file , what i find is boardiag (N5) and blank flash (n6)

Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards

konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
thanks for reply , it's so hard to find OTG with C type in indonesia and LG in here must to check it not sure they can fix it .

Did some tested if this method works for N5x?
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/

konsolen said:
Hy Apayah,
Yes i did. I tried many things, but i get the effect with otg. Found an older thread in which the people write to boot a smartphone over sdcard to recovery. I made my own sdcard. The card in a usb sd adapter and with otg to smartphone.
Then flashed with the lg tool, i thin it was lg tool.
The imei i restored with a dfu cdma software.
But i dont have this nexus anymore because i go with the old.nexus 5 again and sell the 5x.
regards
Click to expand...
Click to collapse
Hi I have this issue on my H791. I do have a USB C OTG cable. Are you saying you were able to point the LG Tool to the file on the SD card through the OTG cable/PC, then flash? Can you elaborate or point me to the thread in reference? I backed up my EFS partition before all this happened, so my IMEI is still intact on a backup. Thanks.

oscillik said:
Thanks for that extra info, I didn't know there was a backup bootloader (shall have to check my Nexus 6P as well!).
Unfortunately I can't get the phone out of QHUSB_BULK mode at all, so hopes are incredibly thin.
I appreciate your extra info on this!
Click to expand...
Click to collapse
I found a way off QHSUSB_BULK that worked for me--with rubber bands. To invoke either boot loader when stuck like this I needed to drain the battery completely, and I figured that would take a very long time without the screen even turning on.
I noticed that if I held in any of the volume keys + power while connected to my PC that the phone was in reality rebooting every 30 seconds--it would come and go from Device Manager. So I grabbed three rubber bands and wrapped them around the phone at each of the 3 buttons and pressed them in.
After a few hours the phone was completely dead and I could power it back on with a brief charge. Into the bootloader it went and I'm back in business.

Nexus 5X not being recognized by PC

I have a really strange problem that none of the other threads in this forum have described. 5X running 7.0 Build NBD90W - Unlocked Bootloader
The 5X was working just fine and I was able to connect to both of my PCs and change the mode from Charging to MTP or PTP from the pull down. Now when I connect, I can see that phone is being charged when connected to the PC, but the pull down is not showing up. If I go into DEVELOPER Options under Networking and try to change it to one of the other settings, nothing happens. My PC does not show the 5X connected in the Device Manager.
I have also tried booting into the Bootloader and using fastboot or adb and neither is able to see the phone. This is happening on multiple PCs.
It's like something is broken inside the phone that it is not communicating. I have tried everything in the forums, I even reinstalled the SDK Toolkit but nothing is working. My last option was to factory reset the phone.
I have also tried to get into Stock Recovery and when I push the power and up button, it gives the message the bootloader is unlocked and then restarts the phone. -- EDIT -- I am able to get into Stock Recovery, I wiped cache and rebooted, still no luck.
Also tried booting into Safe Mode, didn't make a difference.
Any ideas? Thanks....

You didn't mention if you've tried a different cable.

kirkgbr said:
You didn't mention if you've tried a different cable.
Click to expand...
Click to collapse
Good point, I have tried multiple different cables. Same cables work fine with my Nexus 6P.

Got the OTA for N5D91L this afternoon, it was able to successfully update to the November security and after the reboot, still not able to connect to the PC. :crying:

Bump it up!

Oh, i see, i'm not the one with the same problem. i have two 5x with the same problem. both unlocked, rom installed, both started not being detected at some point.

faulty cable
Ok, brought phone to warranty center. They could see a phone and restored OS to original.
Bought another cable to check and it works now ok. Old Nilkin cable still doesn't work (only charges). So, i guess, the problem was with cable in my case.
Good luck finding what's wrong with yours phone.

USB Port went bad need to exchange it

Like title says my pixel 2 XL usb port is going bad / is bad. It's only charging and giving the device has malfunctioned error. I want to simply know since I'm rooted how can re-flash stock recovery? unrooting won't be an issue because of magisk but I need to flash stock recovery since I can't do it via USB.
It appears TWRP is functioning normally , adb sideload or other functions won't work.
Fastboot is not working (waiting for device)
anything that requires the use of usb besides charging is not working.
Any tips on how I can flash stock recovery since I have root with a flashing app maybe from playstore?

patt2k said:
Like title says my pixel 2 XL usb port is going bad / is bad. It's only charging and giving the device has malfunctioned error. I want to simply know since I'm rooted how can re-flash stock recovery? unrooting won't be an issue because of magisk but I need to flash stock recovery since I can't do it via USB.
Click to expand...
Click to collapse
you need to get the boot.img from factory image in whichever month you are on. simply fastboot flash boot boot.img

lucky_strike33 said:
you need to get the boot.img from factory image in whichever month you are on. simply fastboot flash boot boot.img
Click to expand...
Click to collapse
Fastboot also is not working. I have 3 tried different computers.
Is there anyway to do it without USB? since phone only charges on USB but that's it nothing else.
Added screenie to OP
When I had Galaxy Note 4 I remember using Flashify to flash stuff. Would that work if I chose the stock boot img from June factory images?

I had same situation with USB C but already exchange it under warranty. Try this: sign up android P beta user if you are not beta user, or opt out if you are already. Reboot phone, Google will take care of the system reinstall WITHOUT any cable connection/PC. Good luck!

VanGolfer said:
I had same situation with USB C but already exchange it under warranty. Try this: sign up android P beta user if you are not beta user, or opt out if you are already. Reboot phone, Google will take care of the system reinstall WITHOUT any cable connection/PC. Good luck!
Click to expand...
Click to collapse
That's a good TIP I didn't think of it. Thank you. Did you have exactly same error like me? I already have a replacement order in my email (for advanced shipment) do they send you brand new device?

Yes, I had same error, plus not able to hear sound thru USB C port. I get refurbished device. It looks brand new just without charger and cable.

Had the exact same problem with mine, and I'm waiting after my refurbished (ewww) unit. The Pixel 2 really seems to have a low-quality USB-C port or controller: many many owners complaining about that problem on different Android boards.
What annoys me the most is they're sending me a phone that was produced in the same period my faulty one was and that probably has the same USB-C port/controller revision...
https://forum.xda-developers.com/pixel-2-xl/help/questions-rmas-getting-refurbished-phone-t3812486

Same issue with my USB c port. It seems pressed in and does not click correctly. Happend tonight.
Ugh will call Google tomorrow for an RMA