How To Fix Error Can't Copy Files To From Phone To PC/Laptop Via USB​
All Operating Systems Start Here
Remove usb cable from phone/pc
Enable usb debugging mode on phone by
Going to phones settings
Scroll to bottom and select about phone
Tap on build number until it tells you that you are a developer
Go back to phone settings
You now have developer options at the bottom of the list above about phone
Enter developer option and turn on using switch at top right
Scroll down and enable Android debugging
Now Carry On Depending On Operating System
Windows users
In/Re-install the moto g5 drivers from the attachment in this post
Connect phone to pc
Look on your phone screen and a pop-up box will ask you if you want to accept the connection
Agree and make sure you tick always allow connection from this pc
Remove the usb cable
Restart Phone
Once booted insert usb cable
Change connection type in status bar to file transfer
Ubuntu Users
Press ctrl + alt + T to open terminal window
Type the following pressing enter at the end of each line
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
To check it worked type
Code:
adb version
You should get an output that looks like this depending on version installed
Code:
Android Debug Bridge version 1.0.32
Now type
Code:
adb devices
You will get an output that looks like
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
ZY3222SJMV unauthorized
Look on your phone screen and a pop-up box will ask you if you want to accept the connection
Agree and make sure you tick always allow connection from this pc
Then check your device is now authorised type
Code:
adb devices
now you will get an output like this
Code:
List of devices attached
ZY3222SJMV device
Notice unauthorized has now changed to device
Remove the usb cable
Restart Phone
Once booted insert usb cable
Change connection type in phones status bar to file transfer
You can now copy files from the phone to ubuntu
Very thanks bro Installed the drivers but my problem is first of all my phone is charging when connected to windows and it doesn't show any option like file transfer,photo transfer etc. But this problem was coming only from previous week before and all it shows file transfer but it won't work but USB tethering and photo transfer works but now it too doesn't working not even showing the options only charging is working. Pls help me to solve without those functions it's really hard to transfer files to windows.hope u would find solution and reply soon very thanks in advance (sorry for my bad English)
Related
After reading around, I've learnt that MinimalTouch 1.1beta5 is a reliable way to root my new Nook Simple Touch. Since I intend selecting the package version in the beta5 folder, I must choose between the "START" zips: beta5-2 XUFullTouch-PART-1-START and beta5-2 XWFullTouch-PART-1-START. I gather the first zip is ADB over USB, and the second, ADB over WiFi, but have found little documentation on either, except that ADB is a method to connect your home computer to your Nook.
The above link states that all W zips install ADB wireless Uramdisk, and all U zips install ADB USB Uramdisk + ADB widget to enable wireless adb at need. Am I right that ADB over USB is the best choice because both USB and WiFi are available after rooting? If so, would anyone select the ADB over WiFi option?
Can someone please explain how and why one chooses between the two options when rooting the Nook?
On startup the ADB daemon, adbd looks at the property service.adb.tcp.port
If it is set it uses that value as the port number over TCP (presumably over WiFi) to listen for connections.
If it is not set it tries to connect over USB.
I'm not sure how these applications that switch mode work.
They probably kill the daemon and restart it.
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Renate NST said:
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Click to expand...
Click to collapse
Thanks for your help. I've taken a while to make sense of your post since all this is new to me - I rarely use a mobile phone.
I've just looked at contents of both the "START" zip files and noticed they're the same, except that the file uRamdisk in the folder boot of the WiFi option is marginally bigger. You have shown me the difference lies in the property service.adb.tcp.port in the Java source code, and that property determines whether the rooted Nook tries to connect by WiFi or USB. In other words, the two zips are identical except for ADB connection.
But my opening post, in ignorance, attempted to ask a more trivial question. I know whenever I wish to access any laptop computer from my desktop computer under Windows XP, I can connect the two using a network cable from the laptop to my wireless router/modem or, more simply, by activating WiFi on the laptop. Similarly, I am assuming I can connect the rooted Nook to my desktop either by cabling the Nook microUSB port to a USB port on my desktop, or by activating WiFi on the Nook. I expect to connect every few days. Since the USB "START" zip of MinimalTouch 1.1beta5 provides an ADB widget to enable wireless adb at need, what is the point - for the end user - of a separate WiFi only "START" zip file?
In other words, in routinely connecting my rooted Nook to the desktop computer every few days, why on earth would I or anyone benefit from having had the two "START" zip options available in MinimalTouch 1.1beta5?
Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!
__adam_ said:
Hi,
I recently rooted my Samsung Galaxy Tab A thanks to the wonderful folks of this forum. However, now that it's rooted I can't seem to connect to it via adb. For example, I see the device listed when I run "adb devices", but it is listed as "unauthorized". I no longer received the prompt to allow USB debugging. More precisely, I can still access the developer options and see that "USB debugging" is enabled, I just don't receive the pop-up prompt to "Allow USB debugging?" that list my local computer's RSA fingerprint/etc after I plug in the usb... the device just remains unauthorized and never asks me to click ok to allow usb debugging.
As suggested elsewhere, I tried removing the adbkey and adbkey.pub in the .android directory on my local computer and the killing/starting the adb server to generate new keys on the local machine, but that also doesn't seem to help...
Additionally, I noted that there is also no longer a button under developer option to "Revoke USB authorizaiton" (maybe because there are now no longer any keys in /data/misc/adb/adb_keys ?)
Any idea how to get adb shell to work again? Or maybe it not possible after rooting?
Thanks!
Click to expand...
Click to collapse
I finally solved this problem.... I don't think it was particular to the Galaxy Tab A.
In order to get adb working again I had to put the device into recovery mode (power down, then power up while holding power, up-volume, home button). I then went to the terminal application of the Team Win Recovery. In terminal I issues "stop adbd" then "start adbd". At this point the device now shows up on the local host PC when I run "adb devices" (it shows up as "recovery" rather than unauthorized). I can adb root/shell to the device now. This is really all I need to do. I expect this will solve my problem in non-recovery mode as well. Or, at this point I can push my PC pub key to the device and it should be fine.
Hey guys,I hope that all the awesome people here can help me to solve a huge Problem.
My GF had a Galaxy S5 Neo,she thought it would be a great idea to drop it directly on the screen so it broke and won't show anything anymore.
No we need to backup some important files from that device.
Gladly I was able to remove the lockscreen protection with her Samsung Account,but still not able to do more.
The device is on the latest official update,not rooted and no USB debugging enabled.
So I tried to get in recovery and use adb,witch will work every now and than,but I found out that the adb in stock recovery is limited,so now way to do anything there.
If I had enabled USB debugging,I could easily use visor to controll the device.
If I connect it via USB to my PC,it shows up,but as an empty device.
And I can't change the USB mode,because screen is completely dead.
Can I change the USB mode without the screen?
Can I enable USB debugging without the screen?
If I could change at least the USB mode,that could help out at least a little.
Long story short,I need an way to backup file from that thing.
If there is a solution for this,you guys would really help me out.
K-Town Rules said:
Hey guys,I hope that all the awesome people here can help me to solve a huge Problem.
My GF had a Galaxy S5 Neo,she thought it would be a great idea to drop it directly on the screen so it broke and won't show anything anymore.
No we need to backup some important files from that device.
Gladly I was able to remove the lockscreen protection with her Samsung Account,but still not able to do more.
The device is on the latest official update,not rooted and no USB debugging enabled.
So I tried to get in recovery and use adb,witch will work every now and than,but I found out that the adb in stock recovery is limited,so now way to do anything there.
If I had enabled USB debugging,I could easily use visor to controll the device.
If I connect it via USB to my PC,it shows up,but as an empty device.
And I can't change the USB mode,because screen is completely dead.
Can I change the USB mode without the screen?
Can I enable USB debugging without the screen?
If I could change at least the USB mode,that could help out at least a little.
Long story short,I need an way to backup file from that thing.
If there is a solution for this,you guys would really help me out.
Click to expand...
Click to collapse
Hey, i have similar problem, i cant unlock the phone so i have empty device at computer, i was wondering if you have any news on it
You Need OTG
Assuming
- you have stock 6.0.1 and
- you have enabled Developer options,
Here is an easy way:
1. Wait for boot to complete.
2. Once you feel like you're at the Touchwiz home screen, attach a keyboard to your S5 Neo.
3. On your keyboard, press Windows + N (Quick Settings tray).
4. Press Tab twice and Enter (Settings).
5. Keep on pressing Down Arrow for 5 sec.
6. Up Arrow one time and Enter (Developer options).
*** You can now (A) enable USB debugging and/or (B) change USB configuaration to MTP ***
7(A). Down Arrow * 7 times and Enter (USB debugging).
7(B). Down Arrow * 22 and Enter (USB configuration).
8(A). Right Arrow and Enter to allow USB debugging (OK).
8(B). Press Down Arrow and Enter (MTP)
9(A). Connect your phone to your PC *** You MUST keep your keyboard connected ***
9(B). Connect your phone to your PC.
10(A). On your computer, run "cmd" and type "adb devices" to authorize. *** You will see "unauthorized" from your cmd window ****
10(B). On your computer, you will see your device connected.
11(A). On your keyboard, press Tab * 3 and Enter (OK).
12(A). On your computer, type "adb devices" again to see if USB debugging works properly.
Note that this may or may not work for you depending on your firmware/settings.
I haven't been able to get data transfer to work when connected to computer since Color OS 6 update. Pop up warning says resetting USB Debugging is required. Actions already taken :
1. Turn usb debugging on/off
2. Turn developer options on/off
3. Revoke usb debugging (adb devices shows device ID)
4. Enable usb tethering
Any suggestions?
After days of no response and some efforts of painful google-searching , I finally find a solution using adb command which is
adb shell svc usb setfunctions mtp
That being said there should not be any issue with usb / adb driver whatsoever, because I can use file transfer on my LG V30+ just fine using the very same laptop. Also system security check showed usb transfer is being blocked (see attached pics)
I had a stroke 4 years ago and haven't used this tablet since, but I have decided put some books on the Samsung, but now I can't remember how to do it.
Could someone please help me.
Martin.
plug in usb cable one end into tablet other end into PC
usb is connected. Maybe the PC is not connected?
Martin.
what OS?
Windows 11 Pro 22H2
ah windows.. then you may need drivers. not sure, but try this..
on tablet, settings - about phone - tap build number (7x) seven times.
settings - developer options - usb - select file transfer (MTP) as default.
settings - developer options - enable usb-debugging (optional for adb).
you should see tablet in windows explorer now.
if not, you can try adb instead (optional)
in windows device manager, find device with yellow triangle exclamation mark -> Properies -> Update Driver -> Browse my computer for driver software -> Let me pick from the list of device drivers on my computer -> Show all devices -> Have Disk -> select *.inf file
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
(skip this if drivers are fine)
download platform tools and check 'adb devices' from C:\Windows\System32\cmd.exe. if you can see tablet serialno, driver is ready for adb file transfer.
Code:
cd %UserProfile%\Desktop\platform-tools
adb devices
adb push path\to\file /sdcard/Download
https://developer.android.com/studio/releases/platform-tools
I tried the first the setting and won't work. It works on the tablet but doesn't on the PC. I'll try the second part.
I'll try the iPad, it's better than nothing. A new version of Windows will get the Samsung running (I tried it) but I have lots of games to play. Thanks for helping me, alecxs.