Related
[Edit, first post and I got the board wrong. -_-. I thought I was in the troubleshooting section, sorry.]
Hello,
I've bought a used Galaxy Samsung GT-P1000 running Froyo.JPJM5, Firmware 2.2, and Kernal 2.6.32.9, 27.7GB internal memory.
My problem is that I can't get the PC to identify the tablet using the USB cable.
What I do and what happens when I plug in the tablet~
(USB Debugging on)
I connect the USB cable into the PC first. I plug the cable into the tablet. A 'USB is connected' notification shows up. I open it, and click mount.
I look at my computer's monitor and there's absolutely nothing showing that it EITHER identified or not! It doesn't even show a popup.
So I went to my Disk Management to check if it was hidden or something. There's nothing. It just shows my regular hard disks and that's it. No mounted anything. I even looked into my Device Manager and all seems working.
(USB Debugging off)
Nothing happens in either the PC or Tablet.
Things I've tried-
1) Enable USB Debugging.
- Plugging in the tablet, restart computer, and then enable USB Debugging while connected.
- Disable USB Debugging, restart computer w/ tablet connected.
- Plug tablet into PC, and then restart tablet. (with USB debugging and not)
2) Get KIES.
3) Uninstall KIES and only download the USB_drivers.exe thing that comes with KIES.
4) Uninstall everything (including drivers) and getting Android SDK + update everything (about 370mb).
5) Install Ubuntu and trying to get it identified + downloaded Android SDK package and updated everything. (also did lsusb- it doesn't see the tablet)
6) Tried each and every USB port in my PC. (10 ports). [Note: My other Android phone works in any of them)
7) Tried my bro's and sis' comp (win7 32bit)
8) Tried my dad's laptop (win7 64bit)
9) I unplugged tablet, placed the memory card(2GB) of my Android phone into it. Plugged it in my computer and yet it doesn't want to see it.
10) I went to a shop because I thought the USB cable is broken or the port hub is broken. The guy took it and plugged it on his PC using my own cable. He identified the problem and said "It needs its software to be updated". I asked how much, and he said $15. **** that ****. If he can do it, I can do it.
Conclusions up until now:
Tablet knows that its getting hooked up by the computer yet it doesn't send any information to the PC letting it know that it's a mounted drive.
USB Cable is fine.
Port hub is fine since it can detect the USB cable on *usb debugging* mode and I can charge the tablet with the USB cable plugged into the charger.
---------------------------------------------
Note: I tried to root it using z4root which doesn't require a USB connection. It doesn't work. It would work and work until the application crashes and I can't re open it as it always crashes after the first try. I tried using the temporary root option and it would load forever. All in all, doesn't work.
Note2: I attached 2 screenshots. One for my Disk Management window showing my partitions while the tablet is connected (and I pressed Mount on tablet). Second, is for my Device Manager window showing that there no unidentified devices and that the USB devices don't show any Android connected, yet on tablet it says it's mounted.
Thanks.
I don't know too much about how to fix windows.
But when you are using ubuntu,
did you put in this line to your /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
btw, the 51-blabla filename can be 51-xxxxxanything
once done
sudo /etc/init.d/udev restart
plug in your tab to USB port
then if you have your Android SDK, you should have adb?
do
adb devices
does it show your tab?
priyana said:
I don't know too much about how to fix windows.
But when you are using ubuntu,
did you put in this line to your /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
btw, the 51-blabla filename can be 51-xxxxxanything
once done
sudo /etc/init.d/udev restart
plug in your tab to USB port
then if you have your Android SDK, you should have adb?
do
adb devices
does it show your tab?
Click to expand...
Click to collapse
I did what you just said. There's nothing. :|
Hmm..
Out of idea.
If it isn't recognizing the sd card you could try another one. Format it in the tablet, plug it into the computer, put the update on the sd card and update that way and see if it gets recognized that way.
Sent from my SCH-I815 using XDA Premium HD app
czach5932 said:
If it isn't recognizing the sd card you could try another one. Format it in the tablet, plug it into the computer, put the update on the sd card and update that way and see if it gets recognized that way.
Click to expand...
Click to collapse
What do you mean by 'put the update on the sd card'. What update?
Anyways, what I tried is that I used another SD Card (128MB), placed it in, formatted it in the tablet, and plugged it into the computer. Nothing happened on the PC. :|
'adb devices' doesn't show any devices connected either.
(I wanted to confirm that 'adb devices' is indeed working so I tried plugging my Android phone (ST-GT602) and ran adb devices- it showed it. But not the tablet.)
Is there anything other than z4root to root a phone without a USB connection? Or is there anything that might trigger the tablet to let the PC identify it? For example, is there anything that I can place on the SD Card (through another connection.. using my phone for example), then plug it into the tablet, then run that application?
I don't care if it's for rooting or not. Perhaps it would help.
Why don't you spend that $15 at the shop?
Very curious why it works for him.
Sent from my GT-P1000 using xda app-developers app
You might find the Android update online (ICS to GB) or something like that and try to flash a signed update but if your computer doesn't recognize an Android formatted sd card I'm not sure how you would get the card formatted and then get the information to the card. You might search for the update on your tablet, download it and flash it using stock recovery. Maybe getting it updated might work but I have no idea why an out of date tablet won't show up
Also you could try searching online for modified drivers for the device.
Par that I have no idea. Might have to go back and pay the 15 but I would ask the repair guy if you could watch step by step what he is doing.
Hope the best for you.
Sent from my SCH-I815 using XDA Premium HD app
Hey Guys,
I have been using my phone for the past 1 year. My Brother just Wiped Out My Mobile Phone completely though the twrp recovery. Now I am not able to transfer file from or through it. If I am able to do it. I can easily Transfer Rom File onto it and install it.
So Please Say A Way To Transfer File Into My Mobile Please which has no OS And is not being detected in my windows 10 PC.
You can use usb OTG from TWRP and change storage. Also if you connect your phone to PC with usb cable from recovery mode. Your phone shall be detected by your PC as MTP device. Also check if MTP is enable from TWRP.
sahil.kalka;718163.28 said:
You can use usb OTG from TWRP and change storage. Also if you connect your phone to PC with usb cable from recovery mode. Your phone shall be detected by your PC as MTP device. Also check if MTP is enable from TWRP.
Click to expand...
Click to collapse
Should we transfer file normally ... Like just open twrp and connect to my pc. Or any complicated step brother?
My mobile is LeEco Le2 x526 indian snapdragon version...
mufeethmohd said:
Should we transfer file normally ... Like just open twrp and connect to my pc. Or any complicated step brother?
My mobile is LeEco Le2 x526 indian snapdragon version...
Click to expand...
Click to collapse
You can try and tell
Just open twrp and connect your phone to your computer. It should automatically detect your device as MTP. Alternatively, use an OTG USB Drive and install rom from it.
I have rooted Redmi-4A. I have supersu 2.79. My MIUI version is MIUI Global 8.2 | Stable 8.2.1.0 (MCCMIDL).
My USB debugging option is enabled.
I tried the following android applications but failed to get access to the MTP file transfer mode through my phone to PC.
1. MTP enabler Release 3.3
https://forum.xda-developers.com/android/apps-games/app-mtp-enbaler-t3263467
2. QCustomShortcut application
3. MIUI Usb settings
I can select the MTP mode easily in the phone using the default method and the 3rd party apps that I listed above but my PC does not detect my phone. The ADB drivers are installed on my PC. However, my PC detects insertion of USB device and shows a notification upon insertion and taking out of USB cable connected to the phone.
I tried using MI PC suite and it also is not detecting my phone.
Have you tried installing the USB drivers? USB driver is NOT the same as the ADB driver. Google "Redmi 4A driver" and install the USB drivers.
Fobos531 said:
Have you tried installing the USB drivers? USB driver is NOT the same as the ADB driver. Google "Redmi 4A driver" and install the USB drivers.
Click to expand...
Click to collapse
I've installed them as well. They came along with the MiFlash tool. I forgot to mention it earlier
Sent from my Redmi 4A using Tapatalk
archz2 said:
I've installed them as well. They came along with the MiFlash tool. I forgot to mention it earlier
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
Have you tried with USB debugging disabled? Also, does changing the USB mode to PTP help?
Fobos531 said:
Have you tried with USB debugging disabled? Also, does changing the USB mode to PTP help?
Click to expand...
Click to collapse
Yes, I tried with both of these options but failed.
Hmm, that leads me to think that something's wrong on the PC's side. Can you boot up a Linux distro and see if you can transfer files there?
Fobos531 said:
Hmm, that leads me to think that something's wrong on the PC's side. Can you boot up a Linux distro and see if you can transfer files there?
Click to expand...
Click to collapse
I have Windows 10 on my PC. I DON'T have Linux.
archz2 said:
I have Windows 10 on my PC. I DON'T have Linux.
Click to expand...
Click to collapse
You can easily create a bootable Ubuntu USB and test the phone in the live session (i.e. without installing it).
I am currently getting that error with my phone. Not sure but it could happen because of the computer. I have two os in my computer. Win10 and Linux mint. Win10 can detect my phone without an issue but mint not. With usb debugging on I can use adb in linux but still no file sharing.
dokuz said:
I am currently getting that error with my phone. Not sure but it could happen because of the computer. I have two os in my computer. Win10 and Linux mint. Win10 can detect my phone without an issue but mint not. With usb debugging on I can use adb in linux but still no file sharing.
Click to expand...
Click to collapse
Do you have a rooted phone?
archz2 said:
Do you have a rooted phone?
Click to expand...
Click to collapse
Yes and no I mean both. Got same issue in different times with different phones. When the time I use crunchbang I would able to fix it. (by installing things on crunchbang not on the phone). But this time, I did not try to fix actually. I am connecting my not rooted phone only for android studio. It detects it. I can install my apps and can test them. But I cant see my phone in file manager. Thats the story.
the same thing is happening to my wife's rooted 4a and her sisters unrooted one
the same for my not rooted one, I've seen my phone one day in windows 10 explorer (this day it makes 10 seconds to see and when reconnected I could see it one time over 2), but the next day nothing more, I spent hours to try fixing it and have a few computers (all with windows 10), I think it's a miui problem not letting windows acces to the storage.
I have a part of a solution, have ejected my sandisk 64GB SD card, found it was formatted in exFat, empty it in windows, put it back in redmi, after redmi search errors I clicked on the notification and saw a few remaining folders and files, so I went to storage to format the sd card, after this the sd card (and only it) was visible in Windows explorer, but only in MTP (without usb debugging), but the copy from the PC is a kind of erratic (drag and drop 1 folder full of subfolders and files is ok but selection of 10GB gb folders and files to copy stops after the first file copied...), I don't understand how one day I manage to see correctly internal storage and sd card...
edit: today I can see the sd card as empty in windows explorer despite of properties shows it is not, and impossible to copy anything...
So i use now a turnaround, I tried airdroid but device folders were shown as sd card(?), but tried another app "gestionnaire de fichiers" flashlight + clock which can activate ftp service (edit: I have seen after that file explorer from miui could, but it hangs before I found the soulution)
so I type on chrome ftp://192.168.0.45:1234 (1234 is the port number you can choose) with the phone on my box with wifi and all (device ssytem androïd too) is accessible (but to copy to the sd card I would have to use a ftp client).
EDIT: Eureka! I uncheck the fictive sd card optimisation (optimisation de la carte sd fictive in french) option in developper's options and all is ok.
---------- Post added at 05:38 PM ---------- Previous post was at 05:22 PM ----------
So for me to access both sd card and internal device memory in USB in Windows 10 for my not rooted xiaomi 4A miui global miui 9 global 8.1.11 beta android 7.1.2N2G47H
I had to:
-activate developper's mode (7 taps on Miui version)
to activate debugging usb (seems better)
-unactivate fictive sd card optimisation (windows and airdroid do not understand internal memory like a sd)
-format the sd card in the phone (in stockage menu, delete the sd card)
using the MPT mode seems the better option (in "selectionner la configuration usb" in french in developper's mode options) or with the notification when usb is connected.
For me Adb drivers were ok.
And there was a problem with file explorer that hangs when "fictive sd card optimisation" was activated, so even redmi can't access to sd card when this option is on...
So I've got a 3T which currently has no OS installed, just the TWRP3.2.3-0. The problem is that every time I connect the phone to the PC, the PC will only recognise the phone as Unknown USB device (Device Descriptor Request Failed). Due to this I cannot use adb to transfer files to the phone or transfer files directly to the internal storage.
I have tried using Minimal adb but device isn't found, tried different USB ports and cables too. For some reason the recovery does not read devices attached to OTG as I have also tried to transfer files using this method.
Any suggestions as to what I can do to make my PC recognise this device? Thanks
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Hayatzada said:
first of all check your usb cable then use this op3/t tool
Click to expand...
Click to collapse
device isn't found, tried different USB ports and cables too
Click to expand...
Click to collapse
So yeah.
@op USB port in the phone is damaged
Hayatzada said:
first of all check your usb cable then use this op3/t tool
it will install all drivers, unlock, decrypt, install twrp and dm-verity issue solution
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/toolkit-root-recovery-drivers-t3651138
Click to expand...
Click to collapse
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
J-_-M-_-C said:
But I cannot enable USB debugging since there is no OS installed, however I have not yet tested this program.
The USB port was working normally before the OS was removed. This problem started once there was no OS and just recovery. Is there truly no other way I can transfer the ROM to the phone? Thanks for your help
Click to expand...
Click to collapse
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Hayatzada said:
while having TWRP installed pc should recognize your phone, if encrypted phone shows Oneplus 3 in my computer Location without showing internal storage,
Check your USB cable, then boot into fastboot(Boot loader By pressing Power & volume up button together while phone is in off state) connect your cable to pc and phone and run the tool, to install op3 driver select number from your pc
install driver (1)
unlock bootloader (3)
decrypt(10)
install twrp (5)
boot into TWRP from fastboot screen select recovery and reboot
Push superSU (7) (it'll copy superSU into internal memory) install supersu otherwise phone lose root and go back to encrypted state and you cant see internal storage in pc
reboot into recovery and copy your rom, gapps and Magisk 17.1, install them
You are done now
Click to expand...
Click to collapse
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
J-_-M-_-C said:
Thank you for this information, however I get as far as installing the drivers but the PC still shows phone as Unknown USB Device (Device Descriptor Request Failed) and therefore the program does not find the phone. Tried this on two different PC's.
Click to expand...
Click to collapse
please please please check your cable
johnybravo.1981 said:
Go to advance in TWRP then click on sideload and flash the os using sideload command i. e. adb sideload filename. zip
Click to expand...
Click to collapse
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
i have the exact same problem as u my friend i had that problem so i just sideloaded my stock rom and searching for a method to fix this if u find a way to make the device recognised in twrp pls let me know
J-_-M-_-C said:
Since the phone is only recognised as Unknown USB Device (Device Descriptor Request Failed) in the the win10 Device Manager, fastboot devices does not find any attached devices and I cannot transfer files through ADB.
I have tested the cable I am using with another phone and I was able to transfer files to the other phone using the same USB cable.
Click to expand...
Click to collapse
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
johnybravo.1981 said:
Just sideload dude. I came across the same issue 2 days ago.
Or flash using usb otg.
Click to expand...
Click to collapse
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
J-_-M-_-C said:
I have tried using USB OTG but the recovery does not detect my connected usb drive. Regarding sideload, when I boot to recovery and select adb sideload, and connect the phone to my PC I get a USB device not recognised message. The commands adb devices and fastboot devices do not list my phone.
Click to expand...
Click to collapse
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Hayatzada said:
Try this guide if your phone detects as Qualcomm in device manager then proceed otherwise check your charging port (type c port) as you mention usb otg didn't detected and usb cable worked with other phones.
don't forget to clean your type c port if dirty or rusted. :good:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
J-_-M-_-C said:
I have tried to install the qualcomm driver but when I go to Device Manager -> Update Driver -> Have Disk and select the qcser.inf file I get the following message: "The folder you have specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems." I have disabled driver signature verification. No idea why nothing seems to be working.
Click to expand...
Click to collapse
which method do you try? i suggest full method, first one didn't worked for me .
Hayatzada said:
which method do you try? i suggest full method, first one didn't worked for me .
Click to expand...
Click to collapse
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
J-_-M-_-C said:
I have tried Method 1 and arrived till step 6. Then when I try to select the file I get the error I mentioned in my previous post.
Click to expand...
Click to collapse
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Hayatzada said:
try to connect otg keyboard and type in TWRP advance section selecting terminal
if keyboard works, your type c port is ok otherwise change or repair the port
Click to expand...
Click to collapse
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
J-_-M-_-C said:
Tried to connect a keyboard with otg and it did not work with this phone. It worked fine using the same otg cable on another phone.
Click to expand...
Click to collapse
now you should go for a hardware repair of Type C port
Hayatzada said:
now you should go for a hardware repair of Type C port
Click to expand...
Click to collapse
I already said that at the beginning.
For over a year my phone had no issue connecting to my computer via usb cable. I could transfer files back and forth via adb no problem. It stopped being recognized about a month or two ago, So I've been using adb over network.
It doesn't show up in lsusb, but it does charge.
- I thought maybe it was the cable, so I tried a different cable.
- I thought it was the usb port on the computer, so I tried other usb devices. Phone charges when plugged into computer though.
- I thought it might be the connections of the cable to the phone and computer, So I cleaned them with alcohol.
- I thought maybe the connections on the mainboard of the phone, So I pulled the phone apart and cleaned the connections with alcohol.
- I thought maybe adb needed to be updated/reinstalled, so I did that.
So here's my predicament. I was updating LineageOS and there was a problem with the firmware so I reset my phone without thinking. That deleted all my files on the sdcard as well as the system. So I'm only able to use twrp (recovery, no OS). But the phone should be able to mount still since twrp allows MTP.
Any ideas what I can do to get the phone to be recognized by the computer.
Stats:
phone: OnePlus 3T - up to date TWRP only, formerly LineageOS
computer: Ubuntu 18.04, up to date adb and fastboot
winchendonsprings said:
For over a year my phone had no issue connecting to my computer via usb cable. I could transfer files back and forth via adb no problem. It stopped being recognized about a month or two ago, So I've been using adb over network.
It doesn't show up in lsusb, but it does charge.
- I thought maybe it was the cable, so I tried a different cable.
- I thought it was the usb port on the computer, so I tried other usb devices. Phone charges when plugged into computer though.
- I thought it might be the connections of the cable to the phone and computer, So I cleaned them with alcohol.
- I thought maybe the connections on the mainboard of the phone, So I pulled the phone apart and cleaned the connections with alcohol.
- I thought maybe adb needed to be updated/reinstalled, so I did that.
So here's my predicament. I was updating LineageOS and there was a problem with the firmware so I reset my phone without thinking. That deleted all my files on the sdcard as well as the system. So I'm only able to use twrp (recovery, no OS). But the phone should be able to mount still since twrp allows MTP.
Any ideas what I can do to get the phone to be recognized by the computer.
Stats:
phone: OnePlus 3T - up to date TWRP only, formerly LineageOS
computer: Ubuntu 18.04, up to date adb and fastboot
Click to expand...
Click to collapse
I would grab different cables and plug the phone on different computers (Windows, MAC)
I suppose the only way of inserting a file to the phone is through USB at this point.
I would suspect if everything has been done then it might be the port. Might pay to buy a replacement part for the port.
mpore14 said:
I would grab different cables and plug the phone on different computers (Windows, MAC)
I suppose the only way of inserting a file to the phone is through USB at this point.
I would suspect if everything has been done then it might be the port. Might pay to buy a replacement part for the port.
Click to expand...
Click to collapse
It is possible to add files to a phone without ADB by using an OTG USB key and use TWRP File Manager to copy them from /usb_otg to /sdcard.
Sent from my OnePlus 3T using XDA Labs
I had a problem in the past where only my original cable worked to transfer data. I do not even try to use a different cable anymore.
You are running Ubuntu, You see any activity on dmesg when you plug your cable?
You definitely need to test on another computer. As I understood you took your computer apart before testing on a different computer. Sometimes testing on a different USB port is not enough because they may be controlled for the same controller. So if one fails or sends low voltage, for example, both will have the same problem.
I personally would test it on a windows machine with updated USB drivers.