Hey guys, having a little issue here. So I recently wiped my S7 and flashed back to stock using the QG5 firmware. Everything on the phone has been working great. However, between flashing my firmware and now, I installed Android Studio.(not sure if this is relevant or not) My issue is that now I cannot take files off of or put files onto my phone using windows explorer. Every time I try, I get the error message "a device attached to the system is not functioning" I have tried multiple different cables and usb ports, and they all act the same. I connected it to a different computer, and it worked fine, so it is something on my computer. I also uninstalled and re-installed the drivers. Any ideas?
bump still need help. I completely reformatted my computer and it worked, for a while, but now the same issue is back.
Related
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
i've had a few issues with this on my Droid Pro. with windows connection a connection assistant came up with some options that I was able to get it to work as a drive.
Getting it to work with adb is another issue alone. The phone needs to be in "debug" mode. I would search for a tutorial on this because you need to edit files on the computer.
for example on my windows I needed to edit one set of files, while on my linux I had to edit another set of things.
I leave my phone in debug mode because i use it for my android app dev on both computers. try that and see if it shows up on your mac.
I have the following problem:
I wiped my nexus s, everything is empty at this point. CWM working.
However if I connect to the computer it says, device not recognized.
If I plug the phone to the computer, pull the battery, start into recovery mode, there is no error. If I restart the phone, it immediately gives me the error of device not recognized.
Drivers on the computer are good as my other nexus s is working just fine.
SO I have an empty nexus s without access to the sdcard so no possible way to copy files onto it.
Also I read something about odin, but cannot find anything on the net for the nexus s.
Suggestions anyone?
try a different computer, i used my laptop when that happened to me
hopefully it will work for you
thank you for your reply! tried it yesterday on my laptop and surprisingly it worked! after hours of struggling it worked as a charm there... guess a clean driver system is required for a new phone.
Hello,
I have a strange issue - one that I've had for a while now - where neither my PC or laptop will 'discover' my TF700 as a storage device and allow me to copy/paste/delete files from it. This is incredibly annoying as it means I cannot now copy on any new roms.
Strangely - I have managed to flash new recoveries onto the device, but again this hasn't change anything as far as being able to copy/paste files in Windows.. Instead I am stuck with the current (very old) custom ROM I installed a few months ago.
Could this be something to do with the USB drivers I have on my PC/Laptop? I'll be honest - I have tried several.
Could it be something to do with the cable? My official cable is a complete mess and almost in pieces, the replacement I bought (cheaply) doesn't charge properly, but again both work when flashing stuff across...
I am at a bit of a loss... Hopefully someone can guide me in the right direction.
Many thanks in advance for any help
I had the same issue, almost, when flashing TWRP.
All I did was reboot the tablet while plugged into the PC and it was recognized again.
Not sure if it will help you but it is worth a try.
Thanks for the reply.
That was not the issue, I had tried a laptop, my main PC, a couple of cables, reboots, erasing partitions etc. etc.
I finally fixed it today by flashing the latest firmware blob via fastboot, albeit after flashing a jellybean bootloader, as it would not flash properly previously.
Straight after flash of blob it rebooted, took around five minutes finalising configuration and hey presto, Windows found it and everything was well with the world again.
Cheers
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
donk165 said:
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
Click to expand...
Click to collapse
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Mr hOaX said:
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Click to expand...
Click to collapse
Fair enough, well i'm thinking I may move back to CM11S if things don't work out on Blisspop. If I turn off USB debugging and then switch to camera (PTP) mode and then back to MTP mode, my phone then connects fine. I wanted it to connect so I could copy my Titanium backup files off the phone and onto the PC. In the end, my mate told me about Airdroid and I managed to download them through that as a ZIP file. For some reason, the titanium backup folder isn't visible from your computer, I tried copying it to the DCIM folder and it just gave me a 1kb file. I also tried a new folder called backups and it was empty when I looked on my PC, but the files were visible when using Airdroid and also when I used a file browser on my phone.
Weird stuff!
Just wanted to bump this and see if anyone has a solution or even just an explanation.
Whenever I plug my OPO into my PC (with the original cable), the device, A0001 is found but is shown in Device Manager with an exclamation point. If I then right click on it and chose uninstall, and then reconnect the phone, it will connect and work fine for MTP/PTP modes. If I put USB debugging on, the MTP doesn't always work after. But no matter what, if I shutdown my PC, and then come to connect the phone the next day etc, I have to do the uninstall of the driver then reconnect for MTP to work. Pretty frustrating!
Anyone know why the phone isn't remembered by my PC correctly? I'm on Windows 7 x64 if that means anything.
I'm moving back to stock ROM soon so I'll see then if its something to do with the unlocked bootloader or using a custom ROM. I'll report back if I have any luck
Bumping this again, its still the same on 6.0. I don't fancy moving back to stock ROM, I like CM over Cyanogen OS, but this problem is really frustrating. Every single time I connect the phone to the PC, it will come up as A0001 but with an exclamation mark next to it in Device Manager, if I right click and uninstall the driver, then reconnect the phone, it works fine then. But if I restart my PC, it does the same thing where it cant find the right driver for the phone.
Is there anything I can try to fix this?
Hi there.
I have an U11 now and I am quite happy with it.
But there is one problem.
It takes ages till I see the U11 appearing on the PC. USB debugging is on, data transfer chose at the U11, tried several USB connections on the PC tried even another laptop.
Sometimes it is even not showing the phone.
Are here people around who are facing the same problem?
Any solutions?
Thx a lot.
Schuertzi
Yeap exactly the same...
No problem here, each new usb port you connect to loads the drivers and takes a few seconds but after that connection is fast.
Thing that has me peeved is the lack of OTG support. I like to backup straight to an external HDD. No go with the U11.
Tried and waited really long after the drivers were installed. Nothing changed really. Even with using the same USB connection.
May be I did something wrong during flashing TWRP and then the Viper ROM.
Will check and let you know.
Thx
Sxhuertzi
I had the same issue even though i didnt root. I tried on multiple pcs and still got a message saying usb device not recognized. So i returned it and ordered the solar red. I should receive it today and I'll let you know if I still get the same result.
Great, just let us know.
Thx
Hi Guys,
I solved my problem.
I had first the wrong TWRP installed then deleted. Tried then again to install via fastboot. Was not possible.
Then, I installed the official TWRP app from the playstore. Installed the actual TWRP from there. And voila, TWRP installed, rebooted and everything works.
Just for your info. May be you have similar problem.
Schuertzi.
So i definitely had a defective device as this new one connects without any issue.
schuertzi said:
Hi Guys,
I solved my problem.
I had first the wrong TWRP installed then deleted. Tried then again to install via fastboot. Was not possible.
Then, I installed the official TWRP app from the playstore. Installed the actual TWRP from there. And voila, TWRP installed, rebooted and everything works.
Just for your info. May be you have similar problem.
Schuertzi.
Click to expand...
Click to collapse
Hello Sir,
I have almost the same problem which is when I try to connect my HTC U11 to any windows computer it gives me error that the usb is malfunctioned and don't recognize my phone, I also tried to install different TWRP and it doesn't work either, any help would be much appreciated also what type of TWRP you have installed to fix this issue, thank you.
jhill110 said:
Thing that has me peeved is the lack of OTG support. I like to backup straight to an external HDD. No go with the U11.
Click to expand...
Click to collapse
I can use external HDD and pendrives. In fact, the u11 recognises NTFS even.