Why can't I copy files to Galaxy S6?

After updating to Marshmallow on my Galaxy S6, I can't copy files to the phone via PC USB. I am using the factory original cable, have enabled USB debugging, and every time I try to copy files to it from a Windows 7 PC, I can't because the device appears to be write-protected.

Accepted answers

greener6

Thanks,

This works. Verizon's solution seems to be to pull down the notification screen and change USB charging to transfer there. My S6 running Android 6.0.1 Doesn't have a USB icon. You have go through your procedure and change the USB Mode from Charging to MTP EACH time you want to transfer files. At least this is the only way I can get it to work.

All comments

tikibar1

Have you ensured that the USB mode is set to Transferring Media Files?

abjkkc

Yes

Verizon_Support

Thanks for the update abjkkc. What files are you trying to copy?

KinquanaH_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

abjkkc

Just some audio files (mp3).

They don't any digital rights restrictions on them. Just some mp3 files that I ripped from some of my old CD's.

Jeff_Ostroff

HERE's The answer:

The Marshmallow update in March broke the USB config for the Samsung Edge phones, also with my phone, it keeps changing the USB configuration back to "charging" mode from MTP mode, so each time you connect your phone to the computer to view files, it will never connect, you'll have to change the USB setting back to MTP mode first.

Here's what you do to get your phone seen by your PC once again:

1) Go to your phone's home screen select the settings gear icon

2) When settings menu opens up, scroll all the way down to System category and in that category click on "Developer Options". If you don;t see Developer Options as a menu item, then you need to set it up first on your phone.

3) Inside the Developer options menu, scroll half way down and look for "USB configuration"

4) You'll probably see that it says "Charging" which is wrong, and this is why your PC is not seeing your phone, because your phone is stuck in charging mode, not in MTP mode, it should say MTP (Media Transfer Protocol), so change it to this setting.

Once you have done that, your phone will connect automatically to your PC and you should once again see your folder for your phone.

What really stinks about this is that you have to do it every time you connect your phone to the PC now, since that stupid March U. It's a flaw in my opinion, because our phones were all working prior to the March, 2016 Marshmallow update. It used to be every time I connect my phone, the PC sees it. Now I have to [removal required by the Verizon Wireless Terms of Service] with the settings every time to get it to work.

Thank you [removed] software engineers, who don't bother to test the phone the way real people use it.

abjkkc

Yes, I am having this problem, but the bigger problem is that my phone appears to be write-protected because of the Marshmallow update. I can't copy files to the phone from any PC (have tried 3 different computers, 2 using Windows 7, and one using Windows 10). I can live with changing the USB connection type every time I connect. My bigger issue is that I can't copy files to my phone, which is a big deal!

FrustratedDoug

I'm having the same problem with my s6 - your solution sounds like it would work. Big problem, though - I don't have Developer Options as a menu item on my phone, and I don't know how to enable it. Can you help??

Thanks.

doowop111

Yes I can help. This sounds funny, but it’s the answer.

1.. Go to Settings → About phone

2.. Tap Build number 7 times. ...

3.. Go to Settings → Developer options.

4.. In the Settings menu, you can find the Developer options right above About device. ...

5.. Enable Galaxy S6 Developer options.

6.. In Developer options page, drag the switch to right to turn it on.

7..

doowop111

Looks like Android did an operating system update today. (5-13-2016) Finally fixed the problem without all the extra crud you had to go thru.

greener6

Thanks,