Related
Hi! I'vs just bought a new computer and I have to migrate from my desktop PC to the new laptop. The problem comes after restart the PC. I've installed the Android SDK, the PCCompanion, the Gordon's Gate drivers and the fastboot drivers from flashtool, as on my desktop computer with the advanced reinstall to avoid the prohibition to install unsigned drivers. The problem comes here because with my PC I could flash kernels at this point, but, in my new laptop appears another unknow device called Sony Fastboot Interface inside Android Device in the Device Manager. Any ideas?
No one?
What happens when you try to install the drivers ?
Is it in any way colides with flashing and so on ?
IF not then don't worry.
When I finish, appears another unknow device (Android Bootloader Interface) and if I try to flash a kernel, the console gives me waiting for device
I recall installing few drivers.
1 Regular usb
2 Fastboot mode drivers
3 Flashtool drivers
Try googling "xperia fastboot drivers" and download any you can find, i remember downloading some from sony's official webiste.
Here:
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Connect the device in normal mode and fastboot mode and manually select the path to the drivers.
I ended up doing it in windows safe mode, because my pc kept freezing.
GL
Have you tried using flashtool for kernel flash?
Sent from my Xperia X10 using xda premium
Which OS are you using?
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
stargazer127 said:
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
Click to expand...
Click to collapse
isajoo said:
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Click to expand...
Click to collapse
OK, downloaded universal naked driver 0.72, connected gnex, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, and will not allow install of of universal naked drivers, & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
KingWickedd said:
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
Click to expand...
Click to collapse
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
stargazer127 said:
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
Click to expand...
Click to collapse
You have to go to the device manager, double click on the "unknown usb..."
a dialog box may appear and then click on the 'driver' tab.
There u may find update/install driver button.
click on it and another window may open.
then select browse my computer for driver software and go to the respective folder where the drivers are.
then click next and it may install the drivers.
if you have installed the toolkit then you may find a folder in the toolkit's installation folder which has drivers in it.go through it if you want :good:
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
erich_vogt said:
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
Click to expand...
Click to collapse
I used Odin and TWRP in a .tar file. This seemed to work ok but on rebooting the phone now gets stuck on the Google logo. I assume it is a boot loop. The solution to this according to various threads is to either re-flash a stock image or to flash with a custom ROM. I'll try the latter.
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
erich_vogt said:
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
Click to expand...
Click to collapse
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
erich_vogt said:
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
Click to expand...
Click to collapse
I went back to Device Manager and changed the MTP driver to the other alternative which now exists in the system. It's called "MTP USB Device" and is a Microsoft driver. This seemed to improve the situation and allowed me to see all of the contents of the folders in the phone's Internal Storage. I discovered by a process of trial and error that now I could copy files into all the folders except the folder called !ReadyToFlash. I believe this folder may have been created by TWRP when it installed. All the other folders are now behaving sensibly. I copied the Lineage 13 zip into the Downloads folder and booted the phone into Recovery Mode. TWRP 3.0.2-0 was able to install Lineage and everything seems to be working correctly although I haven't tested all the functions yet.
I notice that although the radio can see my 5GHz 802.11ac wifi it seems to be unable to connect and can only connect to the 2.4GHz wifi. I don't know if this a hardware limitation arising from the original modem or a software limitation of the Lineage modem driver. This thread, although it's just me, might give another noob attempting to reconfigure their old Galaxy Nexus a few pointers.
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Try these steps:
-uninstall previous version of SDK tools from PC
-download latest SDK Tools from HERE
-have a USB 2.0 cable available
-follow these steps to verify connectivity
see if these things help
Unless there is a specific reason you're still on Sept 8.0, I'd take this chance and upgrade to lasts 8.1 factory image.
evanxalmighty said:
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Click to expand...
Click to collapse
I'm just spitballing here but....
With phone plugged in, on your pc, under device manage. When you open it up do you see unknown android device? That driver may need to be updated. Also, USB debugging is on, and the option to transfer files? Is your SDK platform-tools up to date?
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
I haven't seen it with this phone yet, but try changing the USB mode on your phone from the notification; I've had a few phones that refuse to work in specific modes.
evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
Have you tried a different USB-C-A cable just for the heck of it. May have to factory reset and see if that solves it.
evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
So your driver is messed up. Did you use the driver below?
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Sent from my taimen using XDA Labs
It won't let me install the driver I get some kind of error when selecting it. I was able to get it to work after plugging it in and out. Now that I updated to 8.1 everything was fine untill I got home. Now it's doing it again. I tried 2 different cables restarted my computer and laptop and can't figure out why it was working fine before without doing anything different.
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
JimSmith94 said:
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
This definitely worked for me -- Thanks for posting!
I am having sort of the same problem. I was on Android 11 on my 2xl, rooted with fast boot boot twrp.Img and installed magisk and super super, all latest. I could not get gaps so I used Android flash tool to attempt to go back stock and it downloaded and flashed it but it is now stuck in loop, I reboot to recovery and it’s stock now and it will not be recognized by adb or fast boot,!0plesase help
Basically, I installed Havoc OS, tried flashing a couple kernels, kept getting systemui crashes, so I decided to dirty flash HavocOS again, and forgot to flash TWRP again before I exited TWRP.
Next, I boot back into my phone, opened Magisk Manager to find that Magisk is not installed, just the manager. I can't install Magisk as I have no TWRP...Which leads me to my next point, trying to boot into recovery brings me no avail as I forgot to flash TWRP. I have zero recovery right now.
Thirdly, HavocOS Suffers from the whole issue of needing SELinux set to permissive, for ADB to work...I can't do that, because I don't have Magisk/root.
Please tell me that someone has an idea here? I'd like to get TWRP back, or back to 100% stock and I can start over, or something other than a custom rom with serious SystemUI crashes and no root...
SOS!
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
As d-m-x stated boot twrp with fastboot boot not fastboot flash. Twrp will load into the phone then you can flash twrp and magisk.
I'd tried Fastboot already, will try again momentarily though.
D-m-x said:
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
Click to expand...
Click to collapse
Fastboot hasn't worked either. Unless I'm doing something wrong, but I just get "waiting for any device" despite having adb on/off, being in bootloader/fastboot mode or being booted into android, etc.
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
D-m-x said:
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
Click to expand...
Click to collapse
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Have you tried different USB A to USB C cables and ports?
Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Az Biker said:
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Click to expand...
Click to collapse
Spoke with Google; getting the phone RMA. Blatantly told the guy it was rooted previously, bootloader unlocked, and running a custom ROM. He said it didn't matter. I will report back on this thread once I have new phone in hand, just to confirm all went well.
Reporting back.
Brought phone to virgin mobile, obviously still heavily modified.
Was given a loaner phone. Signed a paper saying I'd pay 150 for the loaner if it broke. Broke loaner screen same day.
Just picked up a brand new pixel 2 xl they shipped (phone only) because mine was considered unrepairable. I was charged 169 for the loaner phone, to my account with virgin. No cash transaction.
All in all, they honoured googles view of not minding the modifications so long as it's an issue they don't feel is related.
Cheers.