Okay so I am well aware that there are hundreds upon hundreds of articles in different Threads Online about a similar issue. That being pretty much what the title says... " USB device has malfunctioned", "USB device not recognized", "device descriptor has failed (43)" and, in Linux, "unable to enumerate USB device" and then it gives readers at different numbers every time I unplug and replug it.. okay so now for the fun part...
This is a customer's phone (SM-N920X) and they have an issue with the factory reset protection on the device. This device, to be more specific, is using the carrier c-spire and is the SM-N920R7 but at this point that really doesn't make a difference.
WHAT I'VE TRIED SO FAR:
The device fails in Windows 10 Pro 64-bit on every USB port front and back and even a USB 3.0 PCI port. I have uninstalled and reinstalled the drivers countless times on this particular machine and obviously to no avail. I have also tried this phone and a Windows 7 32 bit installation with the same issues. I then tried phone on my Linux box and when I run the DMESG command I get "unable to enumerate USE device, read failure at address XX"
So I then tried it in my Windows 8.1 Asus mini Netbook thingy with the exact same result as all the other windows installations. And just to be sure I tried it also on a Windows 10 32-bit installation with the same outcome. I have tried seven or eight different USB cables and tried all available USB ports on each of the machines listed above. The Note 5 charges just fine when you plug it in. I have tried cleaning up the charging port, adding a key in the registry with a binary that resembles this: SkipBOSDescriptorQuery 0000 01 00 00 00
I have try to use Smart Switch and Samsung Kies letting those programs uninstall and reinstall the drivers each time and again used multiple different cables. I know it is not the ports or the cables because my Galaxy S6 works just fine as did an S7 that I plugged in as well. I cannot reflash the stock firmware to the phone because it will not be recognized by my computer. The only thing I have access to is stock recovery and download mode do to the FRP lock. I have tried wiping data/ factory reset. Wiping cache apply update from Cache, apply update from external storage (cannot mount sdcard error), apply update from ADB (device null/not found when running tmadb sideload "package"..
What the hell can I do? I've never experienced such a pain in the ass phone issue than the one I'm dealing with currently. Please somebody help me LOL.:crying::crying::crying:
rip my balls off
!Led*Eyes! said:
Okay so I am well aware that there are hundreds upon hundreds of articles in different Threads Online about a similar issue. That being pretty much what the title says... " USB device has malfunctioned", "USB device not recognized", "device descriptor has failed (43)" and, in Linux, "unable to enumerate USB device" and then it gives readers at different numbers every time I unplug and replug it.. okay so now for the fun part...
This is a customer's phone (SM-N920X) and they have an issue with the factory reset protection on the device. This device, to be more specific, is using the carrier c-spire and is the SM-N920R7 but at this point that really doesn't make a difference.
WHAT I'VE TRIED SO FAR:
The device fails in Windows 10 Pro 64-bit on every USB port front and back and even a USB 3.0 PCI port. I have uninstalled and reinstalled the drivers countless times on this particular machine and obviously to no avail. I have also tried this phone and a Windows 7 32 bit installation with the same issues. I then tried phone on my Linux box and when I run the DMESG command I get "unable to enumerate USE device, read failure at address XX"
So I then tried it in my Windows 8.1 Asus mini Netbook thingy with the exact same result as all the other windows installations. And just to be sure I tried it also on a Windows 10 32-bit installation with the same outcome. I have tried seven or eight different USB cables and tried all available USB ports on each of the machines listed above. The Note 5 charges just fine when you plug it in. I have tried cleaning up the charging port, adding a key in the registry with a binary that resembles this: SkipBOSDescriptorQuery 0000 01 00 00 00
I have try to use Smart Switch and Samsung Kies letting those programs uninstall and reinstall the drivers each time and again used multiple different cables. I know it is not the ports or the cables because my Galaxy S6 works just fine as did an S7 that I plugged in as well. I cannot reflash the stock firmware to the phone because it will not be recognized by my computer. The only thing I have access to is stock recovery and download mode do to the FRP lock. I have tried wiping data/ factory reset. Wiping cache apply update from Cache, apply update from external storage (cannot mount sdcard error), apply update from ADB (device null/not found when running tmadb sideload "package"..
What the hell can I do? I've never experienced such a pain in the ass phone issue than the one I'm dealing with currently. Please somebody help me LOL.:crying::crying::crying:
Click to expand...
Click to collapse
Your problem is a hardware related issue.. I had this problem once before and I had to open the back of the phone using a heat gun to loosen the glue and then replace the charging port itself!! Nothing else worked and I mean NOTHING but replacing it!!
Replacement charging port
MrMike2182 said:
Your problem is a hardware related issue.. I had this problem once before and I had to open the back of the phone using a heat gun to loosen the glue and then replace the charging port itself!! Nothing else worked and I mean NOTHING but replacing it!!
Replacement charging port
Click to expand...
Click to collapse
Hey thanks for the reply . The phone had FRP triggered so I couldn't do much besides download and recovery mode but I did manage to bypass the FRP the old-fashioned way ! Good old trial and error/tinkering got the job done..You are absolutely correct though I updated the phone to no avail but after all the BS I went through trying to get it to work while FRP=on, I didn't try too hard after LOL.
Sent from my SM-G920T using Tapatalk
!Led*Eyes! said:
Hey thanks for the reply . The phone had FRP triggered so I couldn't do much besides download and recovery mode but I did manage to bypass the FRP the old-fashioned way ! Good old trial and error/tinkering got the job done..You are absolutely correct though I updated the phone to no avail but after all the BS I went through trying to get it to work while FRP=on, I didn't try too hard after LOL.
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
I'm going to assume it's not a Verizon or AT&T locked down pos and if that's the case, you probably could have just used "fastboot oem unlock" or just used fastboot to flash different firmware by going fastboot flash boot boot.img and fastboot flash recovery recovery.img and so on with the other files and wouldn't have had to much trouble lol..
When my charging port went out nothing could "see" it, not the desktop computer not the laptop not even my other phone using a wire to connect both phones together and it wouldn't even charge which is why I figured it needed to be replaced and after I did replace it everything worked fine again.
Enumeration, unfortunately, is a prerequisite in order for one to take full advantage of the fastboot commands...
Sent from my SM-G920T using Tapatalk
!Led*Eyes! said:
Enumeration, unfortunately, is a prerequisite in order for one to take full advantage of the fastboot commands...
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
HI, I have same problem here. Tmobile note 5 on latest firmware. Not rooted. Did you fix the problem?? if so how...???
I"m going crazy here too!!!
---------- Post added at 05:17 PM ---------- Previous post was at 05:15 PM ----------
How do you flash anything if you can't connect the phone to pc????
Short answer: You don't.
Sent from my SM-G920T using Tapatalk
Having said that, there are alternative methods but you said you were not rooted currently so Flashfire is out of the question. I thought of searching for an app that will let you connect to ADB ever Wi-Fi without having to First connect to the computer via USB but I never looked into it. I was never able to flash anything I just bypass the FRP and took OTAs. You could try your luck at different one click root applications but I was unsuccessful with the new version of kingroot. If you can manage to get root access then you could use the official TWRP app to install recovery or use Flashfire to flash whatever you want but like I said it's a was a customer's phone so after I got the FRP done I didn't really didn't look into it anymore.
Sent from my SM-G920T using Tapatalk
**
!Led*Eyes! said:
**
Click to expand...
Click to collapse
How did you end up fixing this? same boat as you frp locked with it not being recognized - did you have to replace the port?
wilfred888 said:
How did you end up fixing this? same boat as you frp locked with it not being recognized - did you have to replace the port?
Click to expand...
Click to collapse
no. I bypassed frp the old fashioned way by connecting the frp locked phone to my mobile hotspot and then as soon as you see the phone switch from checking connection to software update kill your hotspot so it loses connection. the phone will give you an error that says it could not connect to network or something like that but then will allow you to Progress little bit further forward in the menus. when it asks you to set up a pin code for your lock screen do that. now when you lock and then unlock the phone you will have a lock screen and a camera icon in the bottom right corner swipe the camera to take a picture take a picture of anything and then choose to share the picture. there are many options in there and a couple of them will bring you to the screen to setup your Samsung account. either login to your Samsung account or create a Samsung account and then use it's application search feature to find the quick shortcuts application or any application that will allow you to go into the settings of the phone and I'm sure you can figure out the rest from there. it was a customer's phone so I just bypass the FRP and told him his phone won't connect to a computer didn't worry about the port
Sent from my SM-G920T using Tapatalk
So a month ago I purchased a used n920c and decided to root a few days ago. Come to find out I cant connect to pc in any way but will boot. So I have ordered a replacement usb board. A few mins ago I watched the how to video and must say this is not going to be fun. I did get the back off already (without breaking) and now just waiting on the part to come from china (no usa dealers had one for 920c).
Anyone here replaced the usb board yet? Got any hints besides watch videos.
I have one S7 930F like this too. I still have TWRP recovery, I can put custom ROM in CF card from computer. Then flash it in TWRP. The port still can do charge, seems it is low level USB firmware in the phone having issue.
Related
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
donk232 said:
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Make sure you are using the oem usb cable. I had the same problem, changed cables and it worked
some cheap cables are for charging ... bt headsets and other stuff the data cables dont connect, its just for power.
koreancanuck said:
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
donks232 said:
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
Click to expand...
Click to collapse
You gotta make sure that your usb port is directly connected to your motherboard (usually back of your computer).
same usb port that has always worked. ive tried them all by now anyway
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
donks232 said:
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
Click to expand...
Click to collapse
lolol
Duno what happened but I'm glad it worked out for you
I'm having the same problem with my captivate after flashing REDROM. It won't recognize it if I have USB debugging turned on...
i have a theory... were you on a GB or other i9000 based rom/kernel???
well, im still having a problem getting my computer to recognize the phone, i have to mess with it for a a while to get it to work. i really want to flash anew 2.3.3 rom but without being able to get everything working right im stuck in 2.1
is this a problem with my cord or the connection on my phone? or something weird with my phone after flashing it a lot. its currently back to odin stock, i have been trying to master clear it with no luck
TRusselo said:
i have a theory... were you on a GB or other i9000 based rom/kernel???
Click to expand...
Click to collapse
continiuum miui and cyanogen mod are the only things ive tried to flash
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Guys, this problem while connecting to the PC body is stupidly charging .... Even in the download mode Odin does not see a body that could be? Connect other Cappy-all OK.
donks232 said:
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Click to expand...
Click to collapse
it must be a powered usb hub, on my buddies laptop only 1 out of 4 usb ports saw his phone.
if you can get into download mode you arent bricked.
try installing i9000 drivers, or try another computer.
I came up with this a while back. Could very well be the same issue.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Well since you can't use your phone you should sell it to me
Sent from my GT-I9000 using XDA Premium App
I didn't even install drivers, ubuntu got them for me
Sent from my SGH-I897 using XDA Premium App
Hello!,
I got my phone into a weird situation, every time I try to connect to my PC, it's saying "Phone is in USB host mode", the PC tries to recognizes and nothing happens, after that the phone won't charge and stays like that until I rebooted, I can charge it with the original charger after this.
My device:
HTC One AT&T 32GB
ROM: ARHD 41.0
I also tried this method with no results: http://forum.xda-developers.com/showthread.php?t=2481211
Anyone with this situation too?
lumogox said:
Hello!,
I got my phone into a weird situation, every time I try to connect to my PC, it's saying "Phone is in USB host mode", the PC tries to recognizes and nothing happens, after that the phone won't charge and stays like that until I rebooted, I can charge it with the original charger after this.
My device:
HTC One AT&T 32GB
ROM: ARHD 41.0
I also tried this method with no results: http://forum.xda-developers.com/showthread.php?t=2481211
Anyone with this situation too?
Click to expand...
Click to collapse
You mean it's showing up as QHSUSB_DLOAD in Device Manager?
Unfortunately that would indicate a hard brick, no fix, as far as I am aware of.
Welcome to the group of unfortunate people.
I guess the best option would be to send it back for warranty repairs, mine is the same and I'm 99.99% sure it has to do with the charging port.
Unfortunately for me I'm out of the US so warranty shipping is not an option at the moment.
There are other threads about this problem, but so far the only ones I heard that solved this problem was by repair or replace.
You mean it's showing up as QHSUSB_DLOAD in Device Manager?
Unfortunately that would indicate a hard brick, no fix, as far as I am aware of.
Click to expand...
Click to collapse
No, it's not bricked it works ok but only charges through wall charger and if you plug it up to a pc it gets into "USB Host Mode" and then you have to reboot to be able to charge from the wall charger.
My HTC showed the same message. Saying it can not charge into host mode.
HTC only charges powered off.
ferincr said:
Welcome to the group of unfortunate people.
I guess the best option would be to send it back for warranty repairs, mine is the same and I'm 99.99% sure it has to do with the charging port.
Unfortunately for me I'm out of the US so warranty shipping is not an option at the moment.
There are other threads about this problem, but so far the only ones I heard that solved this problem was by repair or replace.
No, it's not bricked it works ok but only charges through wall charger and if you plug it up to a pc it gets into "USB Host Mode" and then you have to reboot to be able to charge from the wall charger.
Click to expand...
Click to collapse
Indeed man, same situation here, I'm actually in Colombia, so not an option to send it, as I can't go back to factory settings without connecting it to the PC.
@nkk71 The device is fully functional, it's just not getting detected on my pc.
lumogox said:
Indeed man, same situation here, I'm actually in Colombia, so not an option to send it, as I can't go back to factory settings without connecting it to the PC.
@nkk71 The device is fully functional, it's just not getting detected on my pc.
Click to expand...
Click to collapse
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
nkk71 said:
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
Click to expand...
Click to collapse
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
nkk71 said:
What Windows version you running?
but be careful, QHSUSB_DLOAD mode is a brick... sooner or later
maybe best to get yourself an ubuntu live usb, and check adb and fastboot connections there. you can use this guide by @tobesedated to create a Live USB http://forum.xda-developers.com/showthread.php?t=2606577
maybe it's just bad/outdated windows drivers.
Click to expand...
Click to collapse
lumogox said:
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
Click to expand...
Click to collapse
Steps 8-15 of my guide show how to set up adb/fastboot in Ubuntu 32bit and to check if your device is recognized. You don't have to install Ubuntu just select to try it. I think that's what scares everyone off, is thinking they have to install the OS...It seems like a lot of work but it really isn't and compared to what you've gone through, it can't hurt....good luck
lumogox said:
I try with 3 different versions of Windows, on my jobI got Win 7, Win XP, and at home Win 8, same issue for all.
Click to expand...
Click to collapse
Win 7 and XP are pretty much OK with any drivers & hboot & firmware/rom, but what is it exactly showing you when you say "USB Host Mode"?
Have you considered uninstalling everything with HTC.... in control panel, and installing newer version: http://forum.xda-developers.com/showthread.php?t=2089508
then see if you get MTP (Media Transfer Protocol) working again.
USB Host Mode (as in Qualcomm High Speed USB Download Mode) is NOT a good sign! it's a brick about to happen.
maybe try changing the cable you are using to your PC!!!
EDIT: and make sure you're phone's USB port is not dirty or similar
nkk71 said:
Win 7 and XP are pretty much OK with any drivers & hboot & firmware/rom, but what is it exactly showing you when you say "USB Host Mode"?
Have you considered uninstalling everything with HTC.... in control panel, and installing newer version: http://forum.xda-developers.com/showthread.php?t=2089508
then see if you get MTP (Media Transfer Protocol) working again.
USB Host Mode (as in Qualcomm High Speed USB Download Mode) is NOT a good sign! it's a brick about to happen.
maybe try changing the cable you are using to your PC!!!
EDIT: and make sure you're phone's USB port is not dirty or similar
Click to expand...
Click to collapse
1. "Phone is in USB mode" appears as a notification on the phone when plugged to the computer.
2. Installed 3 different ROMs with the same result, uninstall everything, and nothing.
3. Don't know how to get back MTP.
4. Brick??
5. I try to charge it, but same thing happens.
6. Clean the port, and nothing.
lumogox said:
1. "Phone is in USB mode" appears as a notification on the phone when plugged to the computer.
2. Installed 3 different ROMs with the same result, uninstall everything, and nothing.
3. Don't know how to get back MTP.
4. Brick??
5. I try to charge it, but same thing happens.
6. Clean the port, and nothing.
Click to expand...
Click to collapse
let's take this down a notch, we dont care what your phone says, we care what shows up in Windows 7 Device Manager (or XP, maybe even Win8):
for example
I really haven't explored what steps are needed to get it back to stock, but mine connects to the pc as long as it's in bootloader so I can flash stuff like Fw but nothing that need to get into the sd card. (as far as I know).
nkk71 said:
let's take this down a notch, we dont care what your phone says, we care what shows up in Windows 7 Device Manager (or XP, maybe even Win8):
for example
Click to expand...
Click to collapse
Well, it's says nothing... doesn't appear anymore on Win 7 devices.
Try cleaning your USB ports?
Sent from my HTC One using Tapatalk
n1234d said:
Try cleaning your USB ports?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm thinking this a port issue, is damage somehow, however, I hope to find a software solution.
New Firmware
Phone that was purchased was not recognized by my computer in recovery and was locked with no S-Off and did not have a Super CID, but assuming that you have all of those things already and are developing these issues then I would try updating the firmware. For some reason, after flashing the 5.11.1540.9 firmware from http://forum.xda-developers.com/showthread.php?t=2485651 and updating to ARHD 71.1 the charging issue all has seemed to disappear. If anyone wants the full run down of how I got from my original non-functioning and unrecognized phone to where it is now I can put in details, but as far as I can tell the issue is just with the firmware if you find yourself being able to intermittently charge in different scenarios when it is off.
Loading New Firmware
Also, for some reason, computer would not recognize phone with TWRP recovery yet I could push files through adb when using CWM recovery. So what happened for me was loading up CWM and pushing the files that I needed into the data folder and flashing TWRP to then install it or rebooting the phone as normal and finding the file with something like a root file explorer. I feel like I may not be very clear with this so post if there needs to be more clarification.
it's a strange issue ,i think it is a hardware problem,happen to me and i try everything possible,without success,than i charge phone when power of and it was the only way ,but led was flashing so it was intermittent charging,i was able to charge only to 97%..i use my phone and somehow next day i was able to charge phone,but then problem occur again...and wired thing is that fastboot devices list is not empty but adb devices list is empty,so phone is not fully recognized by computer,and i forgot to say that day when i was able to charge phone,adb command worked...that day i flashed firmware recovery and rom again ,because i thought it will resolve the problem...
---------- Post added at 11:35 PM ---------- Previous post was at 11:23 PM ----------
ricehoshi said:
Phone that was purchased was not recognized by my computer in recovery and was locked with no S-Off and did not have a Super CID, but assuming that you have all of those things already and are developing these issues then I would try updating the firmware. For some reason, after flashing the 5.11.1540.9 firmware from http://forum.xda-developers.com/showthread.php?t=2485651 and updating to ARHD 71.1 the charging issue all has seemed to disappear. If anyone wants the full run down of how I got from my original non-functioning and unrecognized phone to where it is now I can put in details, but as far as I can tell the issue is just with the firmware if you find yourself being able to intermittently charge in different scenarios when it is off.
Click to expand...
Click to collapse
And do have same problem again after flashing new firmware?
The phone was a gift for my dad and it has been running fine since my last post. No charging issues and the phone does not go into host mode randomly anymore.
Well i also had the same problem...but i did factory reset on the phone and flashed it to completly stock ...and since then no problem..
Sent from my HTC One using XDA Free mobile app
Ok ladies and gents,
I've been on a mission to root my Note 5 N920I for months now.
My problem is no computer will read/recognise the device. The Mac's seem to not even recognise it's plugged in, with Windows, no matter which driver I install it keeps telling me the "device descriptor failed blah blah blah". I managed to root my S4 very easily on Mac with Jodin3 so I know that it ain't no user error.
I've Googled and Googled ways to root without a computer or installing a custom recovery without root, but from what I understand I can't flash TWRP as recovery without a computer and therefore cannot root without a custom recovery.
I've Googled ways to fix the USB issue by making the xml file and putting it into the correct folder, but for that I need to be rooted. Right?
When she's plugged into a computer with USB debugging on or off nothing comes up in my notifications except for charging. I tried using the toolbox which I found on here (sorry can't remember the name) though it seemed like I was getting close, I couldn't get close enough before my temper got the better off me.
If my memory serves me correctly the OTG function worked when i first got the phone but didn't after the first update. My mate's Note 5 also has the same issue. I Googled it and seemed it was common issue on these phones.
I've tried to learn some Terminal/Command Prompt to see if I can fix it that way through Debian or whatever, only got as far as understanding it, kind of. Big ups to all you coders/programmers out there it really is an artform.
So PLZ PLZ can y'all help me, there has to be a way aside from setting this thing alight and getting a new phone.
My next mission, which I only embarked on a couple nights ago is unbricking my dad's Note 4 (N910G) that just hit the **** one day after spazzing out for a few days then would not turn on. I'm getting close though I haven't put much effort into that yet.
Any advice will be greatly appreciated, thanks in advance. ?
Anyone??
$pooLz said:
Anyone??
Click to expand...
Click to collapse
1)First of all have you enabled usb debugging and oem unlocking options enabled from developers options?
2)Install latest usb drivers for your model no on pc, use original usb cable to connect your phone
3) Try different usb hub-ports on your pc, it is recommended to use main-usb port to connect device properly which is mostly located backside of cpu cabinet
4)Does odin recognises ur device? If yes then you can flash twrp and cf autoroot both ( Sometimes Kies or smartswtich like programmes enforces device not be reognised, so uninstall them before trying to connect and flashing thorugh odin)
5)Try to update device drivers manually from Pc's administration
6) Try to connect your phone on another pc running windows and see if it recognises your device or not
I've tried all of that, i have a 09 Macbook Pro hand me down running Yosemite with Windows 8.1 Pro n just put Ubuntu on her today through Parallels. None of which recognise the phone being there.
I've plugged it into 2 HP PC's and both just keep telling "device descriptor failed". They're both kinda old too.
Unless someone has a specific driver they've made or found or could make me?? Clearly I'm a noob.
Closest I've found is https://github.com/452/USBHIDTerminal/wiki/How-to-enable-USB-host-API-support but still need root or system mounted as rw.
Any other ideas? Any ADB codes anyone could help me with ?
Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
mykrov said:
Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
Click to expand...
Click to collapse
I have not seen any other reports of usb dying after OtA update. You say you tried with different PC, what about using different usb cable?
But more bad news for your plans. If you have official v21 update, then you are not rootable anyway.
mrmazak said:
I have not seen any other reports of usb dying after OtA update. You say you tried with different PC, what about using different usb cable?
But more bad news for your plans. If you have official v21 update, then you are not rootable anyway.
Click to expand...
Click to collapse
I tried with diferents usb cables, and nothing happened.
mykrov said:
I tried with diferents usb cables, and nothing happened.
Click to expand...
Click to collapse
Do you know if any of them are sync cables??
codyalan said:
Do you know if any of them are sync cables??
Click to expand...
Click to collapse
They are USB cables that i use on others phones (lg 4x HD and Honor 6X) and work fine with those phones but not on my R1Hd
mykrov said:
Hi, firts of all sorry for my english.
My sister give to me a BLU R1 HD 2GB RAM/16 ROM, it come without Amazon ads (so i think its OEM version). Its running BLU_R001UU_V21_GENERIC.
She told me that one day just not was recognized by PC to transfer files,photos, music. I make a wipe from recovery and still the problem no USB detection at all just charging, no sounds like new USB device was conected, no device on Device Manager.( i do this on diferents PC Windows 10, Windows 8, and Linux Elementary OS , Deeping OS)
I enable Developer Options and change MTP/PTP/Only Charge option and nothing happened; I opened the device to check the pins on the USB connector and check continuity and all seem like be perfect.
I thing that may be when was update to the last software something happen and lost USB recoginition, I want to Root the device and change Recovery but i see that the steps need connect the R1 HD to PC and make some things throw ADB console.
My question is: can i downgrade the original rom from SDcard in the actual Recovery.. to try recover the USB functions. or may be its something wrong on any internal chip that no make the USB conection.
Ty.
Click to expand...
Click to collapse
I have the exact same issue... and it happened just after an OTA Update. After that it showed it was charging only when the phone was shut down.
No USB recognition whatsoever. PC/Mac. Tried several cables.... All USB modes... Factory Reset... Nothing made it work.
I contacted BLU with the issue. As soon as I have an answer (If ever) I will let you know.
If any of you know anything about this please share it here.
Oddly enough, After a cache wipe and factory reset, I have no ads on the lock screen. The app is running on the background but nothing shows up.
elcarmi said:
I have the exact same issue... and it happened just after an OTA Update. After that it showed it was charging only when the phone was shut down.
No USB recognition whatsoever. PC/Mac. Tried several cables.... All USB modes... Factory Reset... Nothing made it work.
I contacted BLU with the issue. As soon as I have an answer (If ever) I will let you know.
If any of you know anything about this please share it here.
Oddly enough, After a cache wipe and factory reset, I have no ads on the lock screen. The app is running on the background but nothing shows up.
Click to expand...
Click to collapse
I think if we can downgrade to a official rom under the actual recovery maybe that fix the USB. But all methods are under USB connection to PC.
mykrov said:
I think if we can downgrade to a official rom under the actual recovery maybe that fix the USB. But all methods are under USB connection to PC.
Click to expand...
Click to collapse
As far as I know downgrading is not possible without making the phone unusable. If by any chance that is possible maybe an update from an SD Card can work.
Ever since I built my new PC running Windows 10 64 bit I can't get Odin to work. The phone connects in download mode but will not flash, it just fails with no error other than fail. I have a ASUS ROG STRIX B350-F mainboard with a AMD Ryzen 3 cpu. I know it isn't a windows issue because I can run Odin just fine on the other three Intel PC's running Windows 10 here and the bios. drivers and OS are all current. Oden is 3.13.1. I'm thinking it might be this mainboard but I would like some input before I purchase another. The thing that is puzzling me is the computer runs everything else but Odin just fine and that makes me think it might be a compatibility issue with the Ryzen cpu in general. Hopefully someone here can shed some light on this.
Misterxtc said:
Ever since I built my new PC running Windows 10 64 bit I can't get Odin to work. The phone connects in download mode but will not flash, it just fails with no error other than fail. I have a ASUS ROG STRIX B350-F mainboard with a AMD Ryzen 3 cpu. I know it isn't a windows issue because I can run Odin just fine on the other three Intel PC's running Windows 10 here and the bios. drivers and OS are all current. Oden is 3.13.1. I'm thinking it might be this mainboard but I would like some input before I purchase another. The thing that is puzzling me is the computer runs everything else but Odin just fine and that makes me think it might be a compatibility issue with the Ryzen cpu in general. Hopefully someone here can shed some light on this.
Click to expand...
Click to collapse
Have you tried a different USB port (in the back of your pc) and/or cable?
sefrcoko said:
Have you tried a different USB port (in the back of your pc) and/or cable?
Click to expand...
Click to collapse
Yes, stock cable, aftermarket one and I've tried all the ports, USB 2.0, 3.0 and 3.1. No hubs either, just strait to the computer. I've been trying different things for about a month to no avail. Even Smart Switch works fine.
Misterxtc said:
Yes, stock cable, aftermarket one and I've tried all the ports, USB 2.0, 3.0 and 3.1. No hubs either, just strait to the computer. I've been trying different things for about a month to no avail. Even Smart Switch works fine.
Click to expand...
Click to collapse
Ok that's odd I have the exact same issue on Intel board. My laptop cost almost 3k pounds so it's one of the best on the market.
Yesterday I got the new Odin and it don't even show my phone as connected which is wired.
I have been using this phone before with this laptop so I am thinking it's a flawed version of Odin going around.
I haven't yet tried an older version of Odin but it use to work in the past so I can't see why it should fail now but have you tried a previous version of Odin yet ?
Edit :
I use my phone and laptop daily with file transfers and I use PDAnet+ which I have used for years and they all work fine no issues as well so it's most likely Odin version.
I remember wired Chinese writing poping up when I first start the new Odin 3.13.1 so it might be a bugged leaked version.
Do you have the same Chinese text pop up on start ?
Zionator said:
Ok that's odd I have the exact same issue on Intel board. My laptop cost almost 3k pounds so it's one of the best on the market.
Yesterday I got the new Odin and it don't even show my phone as connected which is wired.
I have been using this phone before with this laptop so I am thinking it's a flawed version of Odin going around.
I haven't yet tried an older version of Odin but it use to work in the past so I can't see why it should fail now but have you tried a previous version of Odin yet ?
Edit :
I use my phone and laptop daily with file transfers and I use PDAnet+ which I have used for years and they all work fine no issues as well so it's most likely Odin version.
I remember wired Chinese writing poping up when I first start the new Odin 3.13.1 so it might be a bugged leaked version.
Do you have the same Chinese text pop up on start ?
Click to expand...
Click to collapse
I thought the Chinese text was weird too. I did just try to Odin back to 7.1 with version 3.12.5 and still get the same error. At least it's not confined to AMD I guess.
EDIT: It doesn't even verify the files after the md5 check just before flashing, it just fails.
View attachment 4471540
Zionator said:
Ok that's odd I have the exact same issue on Intel board. My laptop cost almost 3k pounds so it's one of the best on the market.
Yesterday I got the new Odin and it don't even show my phone as connected which is wired.
I have been using this phone before with this laptop so I am thinking it's a flawed version of Odin going around.
I haven't yet tried an older version of Odin but it use to work in the past so I can't see why it should fail now but have you tried a previous version of Odin yet ?
Edit :
I use my phone and laptop daily with file transfers and I use PDAnet+ which I have used for years and they all work fine no issues as well so it's most likely Odin version.
I remember wired Chinese writing poping up when I first start the new Odin 3.13.1 so it might be a bugged leaked version.
Do you have the same Chinese text pop up on start ?
Click to expand...
Click to collapse
Firstly,
i have used the Odin 3.13.1 with the " Chinese writing" pop up. a few times now and again to flash Oreo. No issues, works fine for me.
Secondly,
Just a thought / test.?
Have you tried connecting
to the phone ADB .
If you run ADB cmd "ADB devices"
it will tell you " listed devices etc"
My point is it pc Win 10 recognizes that it sees a Android device, surely the correct version of Odin should also.? If not then you can accept that why Odin
does not see your devices.?
I might be off course but......sorry if but, it's
just a thought.?
Misterxtc said:
I thought the Chinese text was weird too. I did just try to Odin back to 7.1 with version 3.12.5 and still get the same error. At least it's not confined to AMD I guess.
EDIT: It doesn't even verify the files after the md5 check just before flashing, it just fails.
Click to expand...
Click to collapse
Well at least your phone is seen by the software. I don't even get the little green box to show my phone is connected.
Only sign I get from connecting to pc is the sound of connection and the data transfer are available as I can see and surf my sd cards on pc side.
I am a bit busy lately so I'll mess about with it when I get time.
I tried flashing Oreo via Odin, it just didn't work. I saw there was an update (not oreo) for my phone, Ive only just got it back after a month but, when I tried after the ota update Odin worked for me.
Maybe that will resolve ypur issue?
Zionator said:
Well at least your phone is seen by the software. I don't even get the little green box to show my phone is connected.
Only sign I get from connecting to pc is the sound of connection and the data transfer are available as I can see and surf my sd cards on pc side.
I am a bit busy lately so I'll mess about with it when I get time.
Click to expand...
Click to collapse
stonedpsycho said:
I tried flashing Oreo via Odin, it just didn't work. I saw there was an update (not oreo) for my phone, Ive only just got it back after a month but, when I tried after the ota update Odin worked for me.
Maybe that will resolve ypur issue?
Click to expand...
Click to collapse
I ordered a different brand mainboard with a different chipset that will be here tomorrow. Hopefully it fixes the issue. If it dose I'll try to RMA this ASUS board and then sell it. Things were intermittent with the Pixel 2XL I had at the time I built this PC but I brushed it off as a problem with the phone. We will see what happens tomorrow.
Hey guys....i had the "failed" message too and fixed it by changing the com port number to com port 1 in my experience i've seen times where phone software will only work on "low" com port numbers....Try that...the basics of the steps are to open device manager on pc with phone connected in download mode (to see the modem device to change its com port), in device manager locate the modem and click Advanced tab then Advanced Port Settings and change the port number to 1 or 2.
After that reboot both devices Pc and reboot phone to download mode.
Has worked for me with Note 7 and Note 8 when faced with same error in Odin.
Sent from my God Mode 8
louforgiveno said:
Hey guys....i had the "failed" message too and fixed it by changing the com port number to com port 1 in my experience i've seen times where phone software will only work on "low" com port numbers....Try that...the basics of the steps are to open device manager on pc with phone connected in download mode (to see the modem device to change its com port), in device manager locate the modem and click Advanced tab then Advanced Port Settings and change the port number to 1 or 2.
After that reboot both devices Pc and reboot phone to download mode.
Has worked for me with Note 7 and Note 8 when faced with same error in Odin.
Sent from my God Mode 8
Click to expand...
Click to collapse
Thanks for the the tip. I was able to change the port but it still fails. I'm out of ideas at this point. If I do need to use Odin my wife's laptop works fine for now.
I wonder if it's got something to do with one of the bios settings...
Misterxtc said:
Thanks for the the tip. I was able to change the port but it still fails. I'm out of ideas at this point. If I do need to use Odin my wife's laptop works fine for now.
Click to expand...
Click to collapse
Did you restart both devices too?
If so, sorry it didn't work...hoped it would help. Which port # did you select btw?
Sent from my God Mode 8
Zionator said:
Well at least your phone is seen by the software. I don't even get the little green box to show my phone is connected.
Only sign I get from connecting to pc is the sound of connection and the data transfer are available as I can see and surf my sd cards on pc side.
I am a bit busy lately so I'll mess about with it when I get time.
Click to expand...
Click to collapse
sefrcoko said:
I wonder if it's got something to do with one of the bios settings...
Click to expand...
Click to collapse
louforgiveno said:
Did you restart both devices too?
If so, sorry it didn't work...hoped it would help. Which port # did you select btw?
Sent from my God Mode 8
Click to expand...
Click to collapse
First off I was wrong, it was not my mainboard. I did end up replacing it yesterday to no avail so now the new board is on it's way back to Newegg . I tried again this morning with my PC after flashing back to 7.1 and back to Oreo via the laptop. The first time failed with the same cable and files from the laptop. The second time it finally worked on my PC. The thing I tried different was using the USB 3.1 port with a USB 3.0 to USB C from my old Pixel phone. Download mode ended up on com 17 but everything flashed good. The only thing I really did different was try the last cable I had. I already tried the same port along with the many others on this machine with every other cable including the original besides the one that now works. Go figure . Anyway thank you all for the help, I do appreciate it.
Misterxtc said:
First off I was wrong, it was not my mainboard. I did end up replacing it yesterday to no avail so now the new board is on it's way back to Newegg . I tried again this morning with my PC after flashing back to 7.1 and back to Oreo via the laptop. The first time failed with the same cable and files from the laptop. The second time it finally worked on my PC. The thing I tried different was using the USB 3.1 port with a USB 3.0 to USB C from my old Pixel phone. Download mode ended up on com 17 but everything flashed good. The only thing I really did different was try the last cable I had. I already tried the same port along with the many others on this machine with every other cable including the original besides the one that now works. Go figure . Anyway thank you all for the help, I do appreciate it.
Click to expand...
Click to collapse
Hot damn I didn't have the phone drivers installed apparently LMAO.
After installing the drivers it worked fine. :silly:
Zionator said:
Hot damn I didn't have the phone drivers installed apparently LMAO.
After installing the drivers it worked fine. :silly:
Click to expand...
Click to collapse
That's too funny. I'm glad it worked out for you too and it didn't cost you $40. It's all good.
I have that problem with ryzen cpu.