Several people have mentioned that they have host mode connectivity problems. USB devices that are connected to the tablet, via an OTG cable or a USB host adapter, are not (or not always) seen by the tablet.
Some people mentioned that the problem started only after the upgrade to 4.1.2.
In my particular case -- stock rom but rooted -- it works immedeately after reboot but stops working sometime later, a strong clue that it is a software (driver) problem.
This has been going on for a while now. I'm wondering: what is the current status? Did anyone complain to Samsung and got a useful answer? Did anyone send the tablet back as defective?
Related
I'm suddenly getting this issue when I plug my tablet into a Windows PC (have tested on two different PCs). I get a "USB Device not recognised" pop up.
More info:
1. happens on both the direct tablet and dock connections
2. have tried 2 USB cables
3. seems to be around the time I updated to .30 but there is no way I can attribute it to this, probably a co-incidence
4. I've done a factory reset and reloaded the .30 firmware from scratch
5. It does still charge though with the AC adapter
I really don't want to RMA the tablet but it seems that is the only way.
Has anyone seen this issue before? Does anyone have any other suggestions?
I'm going to try roll back to .26 but I'm suspecting that it must be a hardware issue.
I could probably live with this, but need to have the PC connection for transferring large files and for adb / flashing etc.
EDIT: seems that it is not possible to do a downgrade from .30 to .26 via the SD card method (let's call it the official method). This might be a .30 issue, I can't tell..
Not an expert here.
Would reloading the PC drivers and enabling USB debugging make a difference?
Thats OK said:
Not an expert here.
Would reloading the PC drivers and enabling USB debugging make a difference?
Click to expand...
Click to collapse
Thanks, I have tried that It flashes up the message immediately when plugging in - on multiple PCs. USB debugging seems to make no difference either. I've isolated the cause to be the tablet itself, not the PC. I'm going to try on another PC later.
Mine wouldn't connect last week for some reason.
I unplugged it and removed the micro SD from the tablet plugged it back in and it showed up.
Weird thing...not sure why it did that.
Hope you can get back from USB Hades there.
So it turns out that the Jelly Bean update fixed my problem - for those in future who may encounter this issue. I'm quite glad that I don't need to RMA the device. I can't understand how even over a full reset and reflash of the .30 firmware the problem was not resolved. In any case, I'm just glad to have a 100% working tablet again! Hooray
After having severe problems with my install (data corruption on internal storage) I tried to recover my tablet. I had a custom rom running before, my laptop was doing ADB shell and fastboot just fine.
When trying to recover, I found out that my USB connection was not working at all. So not even a unknown device, just silence, like tablet was powered off. Not in recovery (TWRP) nor in fastboot. Tested on linux, windows and iOS. Just no signal of a connecting device at all.
After struggeling a lot, (recovering my tablet with only an unreliable recovery) I've got my tf700t in running order. But still no USB connection with pc.
I tested my cable with a tf201 from a friend, my (new) cable is ok.
USB connection is not working on tablet itself, nor in docked state. USB debugging is enabled on TF700.
This summer during holiday (before the corruption of course), my old charging cable was bad, I had to move and turn it before it started charging. It was partly broken. At home I threw it away, so I cannot investigate that cable anymore.
My assumption is that with that defective cable, my usb data lines in the connector received an too high voltage and thus my usb controller is defective now.
USB devices like storage devices connected to my Tf700 work normally.
So; how can I find out that this is actually a hardware error? I'm not afraid to open the tablet, but I think I will not see a problem. I don't know if it can be fixed.
If it is software, which I can also imagine, how could it be fixed?
I think I've exhausted my options, hopefully somebody here has an idea.
From day 1, my TF300T has been unable to connect to a PC. At first I thought it was because one of my cats chewed on the USB cable before I could try (it still charged, just no PC connection) so I didn't do anything while it was still under warranty.
Since then, I've tried 3 different cables, multiple PCs and a Macbook, and I can't get anything out of it. It's not detected at all by the computer - no unknown device, no prompt for drivers, no device connected sound when I plug it in. No reaction on the tablet either, whether USB debugging is on or not. I also tried replacing the USB port on the tablet, but got the same thing. I doubt it's a driver issue since I'm not getting anything at all on either end of the connection.
It DOES connect to the dock ok, and all the dock functions seem to work. I've tried connecting the USB cable to both the tablet directly and the dock, and I get nothing from either port.
I'd really like to be able to flash custom ROMs on it, and I can't find a working way to root or flash it without a functioning USB connection. Could it be the third-party USB cables giving me problems, and if so, is there one that actually works? And if not, is this just a lost cause?
I have run into a weird problem with connectivity on my u12+ recently and was hoping to see if anyone had an idea to resolve it.
The phone will not be recognized by any computer as a device. This is across Win 10, 8 and Mac across various devices. It will only be recognized as a device if booted into recovery/download/bootloader/fastboot.
It WILL charge across all devices and is obviously connected, just not recognized when booted into regular Android.
It IS detected on the same computers and cables when in recovery/download/bootloader/fastboot.
I have tried multiple cables, ports, etc.
The phone is rooted and on the latest firmware (1.21.617) with Magisk/Xposed
Restored with RUU fresh and still had the same issue.
Stock and untouched kernel.
In settings:
USB Connection - Shows None
USB Debugging - Have tried enabling and disabling with no success
Developer Options - Tried enabling and disabling with no success
USB Configuration - Wont show anything other than Charging, wont change if attempted
It did work initially but just can't seem to figure this out! I know the kernel can control some USB stuff (At least on my 10) but since I have not touched the kernel, I was holding off on that to see if I could resolve it first.
Does anyone have any idea?
Could the build.prop somehow have been modified? If so, is the process for viewing and editing it, the same as the 10?
I was thinking of looking at:
service.adb
service.debuggable
sys.usb.config
service.adb.enable
Thanks!
Can anyone please provide their stock build.prop so I can compare mine with theirs?
Thank you
My samsung galaxy s7 (SM-G930F) that was installing LineageOS 18.1 is stuck in a bootloop and I can not get into recovery or pretty much do anything. I can however get into download mode, but the phone is not recognized by USB connection. (From what I read online a year ago, this maybe a hardware issue with some samsung s7 phones. It has not worked for a while for me and I upgrade/update using the phone's hard drive or micro-SD card.) Is there a way to install/get in recovery without a USB connection (since the USB is not recognized). The USB connection does power the device so the issue is likely with the connection and data transfer part of the USB. I have tried other cables and computers and computer ports.
Can I flash a new recovery without USB? Is there any other option? Currently, the phone goes into boot (after the logo) and then keeps on the boot/install into lineage bubble from right to left and does not finish. I don't know if this means that the bootloader is corrupted.
I can get into "Download" mode, but because I can not connect by USB, I can not install a new recovery (unless there is some other option available).
I have/had a similar issue. To the best of my knowledge, you need the USB connector.
My USB port was broken because my meathead self somehow broke the contacts on the USB connector. I'd been using wireless charging to charge it in the meantime.
Replacing the usb connector through the back (soldering a new one on) isn't too bad a feat, and you don't have to mess with the notoriously fragile display at all. Here's a youtube video example
.