Hi, I got this bugger for way too big price (40 bucks for non-working piece of garbage), but I needed it because nobody helped me with reflashing original Nexus 7 I botched up while flashing (can't even get to fastboot mode).
I need to resurrect it from death. Apparently, somebody was tinkering inside, one antenne lead is broken, USB port seems replaced with very wrong one (it fits, it sits, but clearly it is not original) and the main, biggest problem is that the OS is corrupted.
All I keep getting is Google logo, can't boot into normal mode, can't boot into recovery mode. Can get to fastboot interface though. But there is one problem - the USB debugging was never activated, so when I plug it into computer in fastboot mode, all I get is "Unknown USB device (device descriptor request failed)". When I try to manually install Universal Naked Driver, it keeps *****ing about wrong driver version or not compatible hardware. What I have to do to get it working except sending it to Asus and pay 5 times the tablet's price to get it fixed?
It was going to be replacement for that botched Nexus 7, but now it seems that it will cost way more...
Have you not tried the Nexus Root Toolkit by Wugfresh? I reckon you should give it a try good luck.
Yeah, that came around my mind too, but there is one problem. USB debugging was never turned on and now when I plug in the tablet, it shows in device manager as Unknown USB device (device descriptor request failed). And because there is no working communication (it doesn't show up as tablet), I cannot ADB DEVICES it, returns me empty list.
krivulak said:
Can get to fastboot interface though. But there is one problem - the USB debugging was never activated, so when I plug it into computer in fastboot mode, all I get is "Unknown USB device (device descriptor request failed)"
Click to expand...
Click to collapse
USB debugging on/off is relevant only in ADB mode and has no impact whatsoever in fastboot mode. Please boot it in fastboot mode, connect to PC and quote USB device descriptor number from device manager.
If it is 18D1:4EE0 then you have to resolve driver issues on your PC
If it is 0000:000x then you have to fix hardware problem in your Nexus
I posted more info in this and this thread.
USB Device Tree Viewer shows it as vid_0000&pid_0002, so there is hardware problem with the tablet.
So, if I understand it correctly, it can be caused either by badly seated cable or bad USB port. Sice the one that is there is clearly changed for the wrong one, I will try to order proper one and see what will it do.
By the way, I already tried to reseat the ribbon cable, no luck there.
Related
Hi Everyone,
I seem to have bricked a nexus 2013 wifi. At first, it was having movie playback issues so I restored it to lollipop using factory image on the google site. I decided to get OTA up to the latest MM. So far so good. But I though about putting a custom rom to it. So I installed TWRP 3.02 for flo and flashed PN MM with the recommended GAPPS. Kernel was what came with it. It worked fine until this morning when I realized that the touchscreen was not responding. I went to BL mode and into recovery. TWRP came up but touch was not responding as well.
So, I connected the device to my PC. It now shows unrecognized device. It still charges and all that but It is now stuck on the google logo. when I go to TWRP, touch wont work. I have tried another cable, still the same. My N6 is detected without issues using the same PC and cable. Since there are no drivers, I cannot reflash anything...
Any thoughts? Or am I just lucky to have bricked it? Appreciate any inputs that will be thrown in this direction. Cheers!
Hi, N7 motherboard gets touch, USB, accelerometer and compass data via the wide silver cable which often suffers from poor contact. Please try this first. If it is still not fixed, then in fastboot mode run and post the output of the following commands:
Code:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache
Thanks for the help. hmm.. i pressed that part and it booted up to PN, touch is working as well. Not sure if that fixed it but if it happens again im gonna try to press that area. however, its still not detecting the device. I see it in Device manager, it says unknown device and will not take any driver, so fastboot is not an option for me atm.
so just an update. when I was able to boot up, it will not go landscape no matter what. I downloaded check my android and it the tests for compass and sensors were not responding. I decided to open the back cover, it was fairly easy. The thing is I have not the right tools to reseat the silver flex cable and I fear I might damage it, so I tried putting folded paper on to where it connects to on both ends. Now the thing works with landscape and so far, have not experienced touch issues or no boot issues.
I still do not have access to fastboot, though, as it still isnt detected by my computer. so I may have to stick to putting stuff to it over the air. Or should I just reseat that cable? Does it just slide out?
welxiii said:
I still do not have access to fastboot... should I just reseat that cable?
Click to expand...
Click to collapse
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
noahvt said:
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
Click to expand...
Click to collapse
The next step:
disconnect the ribbon cable from both the mobo AND daughterboard
spray the cable's and PCB connectors' contacts with Electronic Cleaner
reconnect and relock
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
Hi,
I really appreciate the assistance. Well, here's what I found.
[*]What's the VID/PID of the non-detected device? USB\VID_0000&PID_0002\6&688A3B8&0&2
[*]Does ADB work if you start TWRP? I don't think it does. In TWRP, I still get a message on my computer that the device has failed. DM shows the device as unknown usb device (device descriptor request failed)
[*]Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it? no it doesnt. same error as above.
[*]Is an OTG flash drive recognized? yes it does.
[*]Maybe Windows has a driver problem - does it work from live Linux? I'm still working on this. btw the same setup works on my phones and they are detected just fine.
update:
Suddenly its now detected by my pc. I connected my usb otg. At first,. It wasnt detected so I tried the usb on my nex6 and it worked. I connected it back to the 7 and voila! No error and DM now shows it as an android device. Whew!
But I have one question, is it safe to leave the folded papers i placed on both ends of the silver connector?
welxiii said:
Suddenly its now detected by my pc...
...is it safe to leave the folded papers i placed on both ends of the silver connector?
Click to expand...
Click to collapse
Yes.
As I mentioned earlier, the silver cable also connects USB data, so if you experience USB detection problems again, then do full re-seating with clean-up.
Cheers :highfive:
Thanks again for the assistance. Hopefully, it doesn't come to that.
unbricked my google nexus 7 tablet
if anyone has bricked there nexus 7 wifi tablet.....you can now unbrick it with the skipsoft toolkit. my tablet was bricked for awhile (it was stuck on the google logo and when I tried to boot into the twrp recovery it showed the android bot with an exclamation point so I was screwed big time) so I just brought another one (different version). after awhile I gave up hope, but today I decided to unbrick it (or atleast try to). at first I was using the nexus toolkit like I did before and I was having problems with it being recognized via adb and it wouldn't flash the stock recovery.img. than I remembered that I also had the skipsoft toolkit installed on my computer and the nexus 7 tablet was also supported on that toolkit so I decided to give it a try. at first, since I had it plugged in, it wouldn't recognize that it was plugged in not realizing that I had to download all the images and recoveries it needed to be able to root it and return it to stock if necessary so I did that and when I finished installing everything it detected that my device was in fastboot mode. I flashed the stock recovery image and it booted up like it was suppose to. I'm writing this just incase so one has bricked there device and has lost all hope in fixing there mistake. I love android and recently have a lg nexus 5x that's rooted with a custom rom on android 7.0 nougat. android is awesome
who ever developed the skipsoft toolkit....your awesome and thankyou for making this possible.
I have a problem.
My screen is broken. Now I want to send him to OnePlus.
But before that I want unroot it. Or at least reset to factory defaults. But both things fails.
I have the latest FreedomOS Rom. Since then I can no longer use TWRP. When I start my phone to the recovery the screen goes black and nothing happens anymore.
The same happens when I put it back to factory settings through the settings menu .
I've read there is a modified version of TWRP.
From here begins the real problem. Windows doesn't recognizes my phone.
In Device Manager it appear as "unknown USB device (failed request for device descriptor)"
What I've tried:
Boot in to Bootloader
Original (Dash) USB cable
Other USB cable
WIndows 10
Windows 7
USB debugging on
USB debugging off
OEM unlocking on
OEM unlocking off
USB configuration: File transfer
USB configuration: MTP
USB Configuration: Charge
Anyone have an idea?
Maybe it's the ROM. But I cannot flash another ROM because I can not get into TWRP.
Maybe it's an option to flash the modified TWRP without a computer. So right from the bootloader. But I do not know if this is possible. And how it should be done.
You're in wrong device forum. This is specific for One M8 not OnePlus.
For One M8, most of the time HTC USB drivers will fix that unknown USB device problem.
Maybe something like that for OnePlus, so ask in your device specific forum.
Och, I'm sorry. Please close this topic for me. I'll make a new one in the right place.
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!
To provide you with some context, I messed up a custom ROM install on my Redmi Note 5 Pro/Whyred Global version/ where the phone starts up and get stuck on the Orangefox Recover logo screen.
I thought I could just reinstall Orangefox via fastboot and format the phone to start fresh but the phone is refusing to be recognized by Windows in fastboot. It's the same Windows 10 PC that I used to unlock the bootloader on this phone and flash a custom recovery a year ago, and now it refuses to recognize my phone altogether.
Its giving me the USB Device Descriptor Request Failed error.
The drivers are not the issue here on my PC, I recently used this PC to unlock my Poco F3 and the procedure on that went flawlessly. But now it's refusing to recognize this phone. To rule out the little stuff, i changed cables, changed and tried different PCs, decided to use a USB 2.0 port on my PC thinking that might be the problem but still no luck.
I was planning to try this guide, but for that, I would need the hardware ids for the phone when its in fastboot mode. So if anyone has the phone, please I beg you give me the hardware Ids. I really want to fix this phone and give it another life.
Just in cast this fails, my last option would be to get the micro USB port replaced. I have gotten the USB port on this phone replaced twice as it used to cause problem when charging, so my final doubts are going to this.
My only evidence against a borked USB port is that the phone used to fast charge fine with this port. And since fast charging utilizes the data cables to negotiate with the fast charger, but I might be wrong about this.
So if anyone can help me regarding this issue, I would highly appreciate it.
https://forum.xda-developers.com/t/fastboot-not-detecting-my-phone.4544585/post-88035749
aIecxs said:
https://forum.xda-developers.com/t/fastboot-not-detecting-my-phone.4544585/post-88035749
Click to expand...
Click to collapse
I tried that , but I am still getting that error. Do you think this might because of faulty USB port?
probably Windows issue. use linux
https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4
abeel_siddiqui said:
Its giving me the USB Device Descriptor Request Failed error.
Click to expand...
Click to collapse
That's an indication of basic USB enumeration failing.
It could be bad cable, bad port or your device has failed initializing USB.
It's not an indication of anything to do with Windows drivers (at this point).
Renate said:
That's an indication of basic USB enumeration failing.
It could be bad cable, bad port or your device has failed initializing USB.
It's not an indication of anything to do with Windows drivers (at this point).
Click to expand...
Click to collapse
I have also tried swapping cables, the micro USB fault might just be faulty on the phone.
aIecxs said:
probably Windows issue. use linux
https://gist.github.com/smac89/251368c8df2ccd645baedc3e1238fdb4
Click to expand...
Click to collapse
That could be possible, I will try booting into a live Linux environment and try it there.
Hello XDA community,
I am facing an issue with my device after flashing the wrong ROM. The device entered EDL mode, and when I connected it to my computer, it initially showed up under Ports in Device Manager as COM 10. However, now it is showing up under USB Controllers as an Unknown USB Device (Device Descriptor Request Failed).
I have tried the following solutions without any success:
Reinstalling the device driver by uninstalling and letting Windows reinstall it automatically after a restart.
Manually updating the driver through Device Manager.
Performing a hard reset and attempting to enter bootloader/recovery mode.
Trying different USB ports and cables.
Installing the Qualcomm QDLoader driver.
Unfortunately, none of these solutions have worked for me. I would greatly appreciate any advice or suggestions on how I can resolve this issue. Thank you in advance for your help!
"Device descriptor failed" is the most basic USB error possible in Windows.
It means that the device has asserted pullup on the D+ but is not responding to anything.
As proof of concept I just did that with a resistor and a cable.
This means that the USB interface is enabled but it is totally dead.
Not ADB, not fastboot, not EDL, nothing.
Renate said:
"Device descriptor failed" is the most basic USB error possible in Windows.
It means that the device has asserted pullup on the D+ but is not responding to anything.
As proof of concept I just did that with a resistor and a cable.
This means that the USB interface is enabled but it is totally dead.
Not ADB, not fastboot, not EDL, nothing.
Click to expand...
Click to collapse
Not everytime. It may be due to faulty usb cable and sudden power surge on the usb port.
mvikrant97 said:
Not everytime. It may be due to faulty usb cable and sudden power surge on the usb port.
Click to expand...
Click to collapse
Well, ok. Cut the white wire on a cable and you'll get this all the time.
In any case, it means, "I can sense something is plugged in, but I can't get to "Square One".
Renate said:
"Device descriptor failed" is the most basic USB error possible in Windows.
It means that the device has asserted pullup on the D+ but is not responding to anything.
As proof of concept I just did that with a resistor and a cable.
This means that the USB interface is enabled but it is totally dead.
Not ADB, not fastboot, not EDL, nothing.
Click to expand...
Click to collapse
what is the solution?
You've apparently bricked your device.
You need to flash everything using EDL mode.
You probably need to use EDL test points to get there.
It's bypassing EDL mode on boot because it thinks things are ok.
But as it gets further along it discovers that it's a train wreck and just stops.
If you had killed it more it would have gone directly to EDL mode.
Renate said:
You've apparently bricked your device.
You need to flash everything using EDL mode.
You probably need to use EDL test points to get there.
It's bypassing EDL mode on boot because it thinks things are ok.
But as it gets further along it discovers that it's a train wreck and just stops.
If you had killed it more it would have gone directly to EDL mode.
Click to expand...
Click to collapse
I don't have any issues myself, but do you think one of these "DeepFlash" Cables (e.g. on eBay) work? They are able to trigger EDL Mode apparently.
I've also read that you can just DIY such cable.
Long time ago, my phone had also gotten hardbricked due to an aborted Fastboot Flash.
I don't remember if Device Manager said "Device Descriptor Failed", but it wasn't in EDL Mode and I had to remove the backglass and trigger the EDL Test-points. All good though now.
I've never resolved exactly where the code for detecting a grounded D+ line in the USB is.
It could be in the PBL (in ROM), the xbl or the abl.
I'm not sure if all devices have it.
I'm quite sure that I've never gotten it to work.
That may be because of the devices I've tried or my lack of coordination.
OTOH, I have half a dozen devices that I can hit the EDL test points.
YMMV