Hi everybody ,
Sorry for my english i'm french!
I realized that I just cannot edit(rename)a new folder that I have in my Note 3 : it's freeze my explorer OS! (or on the unterne memory or micro sd card) from my Windows OS 8.1 pro!Yet this is a clean install and fresh just do on myPC!
This plant my explorer! I try whith soft http://blog.qdigi.com/2012/09/accessing-your-android-device-from.html and it's bug too!
But when I try to rename the folder from another PC on Windows7 it works!
What do you think,do you feel the same with windows8.1?
it makes me that on 2 PC Windows 8.1! then on seven no problems!
Itry to install the last usb SAMSUNG USB DRIVERS 1.5.27.0 INSTALLER and it's the same probleme!
I try to re install with Kies and it's the same issue!
I can add a folder and delete, but not rename it! Why?!! :crying:
I have the same problem's with my note 3 but the same with my galaxy s3 in windows 8.1.In windows 7 i didn't have this problems.
ditto here. I use ubuntu in vmware to do stuff Iol.
Sent from my SM-N9005 using Tapatalk
Same here with Windows 8.1
Gesendet von meinem SM-N9005 mit Tapatalk
Use MyPhoneExplorer for that.
To transfer big files it isn't a good idea, because it's not faster than 1,1 MB/s
But to create folders and transfer little files it's very good!
MyPhoneExplorer website
and here the app for your phone (needed to connect your mobile with your pc)
http://https://play.google.com/store/apps/details?id=com.fjsoft.myphoneexplorer.client
i hope you enjoy it!!
when i try to instal flashtool drivers for my xperia z1 i get errors and installation fails
sony net - failed
sony (winusb) - failed why is this ?
Are you running Windows 8/8.1 64 bit ?
Then you have to disable driver certificate check.
Here in the forum are tutorials about this issue.
Regards
Meet
Gesendet von meinem GT-N7100 mit Tapatalk
Actually you don't need drivers installed manually, keep pushing volume down and connect via usb to pc, the windows will install the drivers automatically and you are ready to go. Remember to keep pushing volume down all the time in the process.
My girlfriend broke the screen of her phone and the digitizer. She never turned on USB debugging mode and has a lock on her screen. With the help of this forum I was able to get the phone into recovery mode and detected with ADB. But every time I try to pull the photos from her phone I get the error in the command prompt "error: closed". How can I fix this? I tried to kill and start the server but that did nothing. Also what directory or prompt do I to write to pull the right folder, because I am not sure where the DCIM folder is located.
Please help me out and thanks in advance.
Did you try to pull the whole internal sd ?
Gesendet von meinem GT-I9505 mit Tapatalk
devgee said:
Did you try to pull the whole internal sd ?
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
I just tried adb -"d" pull sdcard/ C:\RecoveredData and same error "Error: Closed." :/
I have tried all the possible solutions described in the forum and in other places, but pitifully without success.
To this day, I have not been able to get Windows 10 Pro N to recognize my Nexus 6p.
The MTP driver appears as unsigned digitally. The ADB driver appears as correct.
As a solution I reinstalled Windows 10, provisionally solved. But then Windows was updated and the error returned.
Any suggestions?
Have you tried installing the Google driverset via the SDK Manager?
redduc900 said:
Have you tried installing the Google driverset via the SDK Manager?
Click to expand...
Click to collapse
How do I do what you mention?
Enviado desde mi Nexus 6P mediante Tapatalk
https://dl.google.com/android/repository/tools_r25.2.3-windows.zip
Once you have downloaded and installed the Android SDK Manager above you run the program as an administrator. Choose what you want to install. If you don't already have them you want Android SDK Tools and Android SDK-Platform-tools at the top (which would give you the most current ADB installation) and Google USB Driver is at the bottom under extras. You don't really need anything else unless you plan on doing Android programming. Just check what you want to install and click the button that says install packages.
---------- Post added at 11:36 PM ---------- Previous post was at 11:26 PM ----------
You could also go this route:
http://www.technobuzz.net/install-google-nexus-6p-usb-drivers/
which will install the Nexus drivers plus Huawei's phone interface program HiSuite. I must have installed this way because HiSuite opens every time I connect my Nexus 6P to the computer and I just close the program since I never use it.
jhs39 said:
https://dl.google.com/android/repository/tools_r25.2.3-windows.zip
Once you have downloaded and installed the Android SDK Manager above you run the program as an administrator. Choose what you want to install. If you don't already have them you want Android SDK Tools and Android SDK-Platform-tools at the top (which would give you the most current ADB installation) and Google USB Driver is at the bottom under extras. You don't really need anything else unless you plan on doing Android programming. Just check what you want to install and click the button that says install packages.
---------- Post added at 11:36 PM ---------- Previous post was at 11:26 PM ----------
You could also go this route:
http://www.technobuzz.net/install-google-nexus-6p-usb-drivers/
which will install the Nexus drivers plus Huawei's phone interface program HiSuite. I must have installed this way because HiSuite opens every time I connect my Nexus 6P to the computer and I just close the program since I never use it.
Click to expand...
Click to collapse
I tried the last option without success.
In the first description, what is the way to install the tools
yamilmanzur said:
I tried the last option without success.
In the first description, what is the way to install the tools
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page527
RoyJ said:
Read this thread
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page527
Click to expand...
Click to collapse
i will try
If you have any drivers installed now uninstall them by opening driver manager going to view->show hidden devices. Go to Android Device, and delete all the entries in there.
Now start by installing minimal adb and fastboot.
Then download this, extract it to a folder, plug in your phone. Make sure USB debugging is on
Then begin to follow this guide until you get to the have disk part. Close the video now. When you get to the have disk part, select android_winusb.inf from the folder I linked you to on Google Drive. Then you just next thru everything. This should work for your 6P.
I have solved using the Nexus toolkit. With this tool I can finally install the MTP drivers and that Windows recognizes my phone
Enviado desde mi Nexus 6P mediante Tapatalk
Honestly I rarely even connect my 6p to my desktop over usb anymore. MTP on win 10 is so atrocious. If I'm trying to transfer larger files or a picture folder windows will simply hang in the "calculating time required to copy" step, then trying to cancel will freeze everything. I've tried drivers, solutions etc to no avail. Best thing I've found is transferring files over wifi direct by using the ftp module in es file manager. You should definitely try it out, saves me lots of headaches!
longjohnsteve said:
Honestly I rarely even connect my 6p to my desktop over usb anymore. MTP on win 10 is so atrocious. If I'm trying to transfer larger files or a picture folder windows will simply hang in the "calculating time required to copy" step, then trying to cancel will freeze everything. I've tried drivers, solutions etc to no avail. Best thing I've found is transferring files over wifi direct by using the ftp module in es file manager. You should definitely try it out, saves me lots of headaches!
Click to expand...
Click to collapse
I did not know the function of transferring files via FTP. I was testing send anywhere app and was pleasantly surprised
Enviado desde mi Nexus 6P mediante Tapatalk
longjohnsteve said:
Honestly I rarely even connect my 6p to my desktop over usb anymore. MTP on win 10 is so atrocious. If I'm trying to transfer larger files or a picture folder windows will simply hang in the "calculating time required to copy" step, then trying to cancel will freeze everything. I've tried drivers, solutions etc to no avail. Best thing I've found is transferring files over wifi direct by using the ftp module in es file manager. You should definitely try it out, saves me lots of headaches!
Click to expand...
Click to collapse
I find transferring files via MTP on Windows 10 much faster and easier than using WiFi method. There must be something wrong with your drivers setup. It always works flawlessly for me.
---------- Post added at 04:05 AM ---------- Previous post was at 04:04 AM ----------
yamilmanzur said:
I have solved using the Nexus toolkit. With this tool I can finally install the MTP drivers and that Windows recognizes my phone
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
That's good to know. Never really tried the various tool kits
quick update: MTP kept hanging at the calculating time required of a big transfer. Completely uninstalling and reinstalling every android driver through a toolkit has seemed to work so far.
mali_ said:
How did you do it? I'm using windows N version and I can't get mtp to work. I don't want to install the media feature pack.
Click to expand...
Click to collapse
I'm sorry but I can not help you, since my current phone is another and not the Nexus 6p
mali_ said:
But the issue is not limited to the nexus 6p. It is a windows issue in the N versions and occurs for any device that uses MTP.
Click to expand...
Click to collapse
May be, but I remember that with the Nexus toolkit I had solved it
mali_ said:
How did you do it? I'm using windows N version and I can't get mtp to work. I don't want to install the media feature pack.
Click to expand...
Click to collapse
If you can't get it figured out using the Google USB drivers, install the Nexus Root Toolkit (NRT) by WugFresh. It has a driver installation and testing tool. It will work. There is also a NRT support subforum dedicated to the N6P. You can also use MTP in TWRP natively if you have TWRP installed.
mali_ said:
Yes, I already tried that before posting. The driver installs fine but my phone isn't detected, exclamation mark in device manager.
Click to expand...
Click to collapse
Well you didn't try it properly because it works 100%. If you remove all the old drivers from Device manager *and* using USBDeview, it will work. Try it again and follow the instructions to the letter. You should also swap cables just in case, so you can rule out a defective or damaged cable. You'd be surprised how often this happens. NRT will install drivers for use with ADB and Fastboot. After you finish, run Step 4 to confirm. The toolkit is just automating what most people do manually. This is not an issue with Windows, you probably have an old USB driver conflicting, and that is what USBDeview is used for. What about using MTP in TWRP... Is it working?
I have an MTCD-KGL unit (version 1.92a_4) but I can't run easy connected as its not installed. I've tried installing a couple of versions which didn't work, but then discovered there are a vast number of different revisions with different 2 letter codes in the file names:
I can't put the link as I haven't posted 10 posts yet
www . biliworld dot com/file/661459919981999519/
e.g. FY, TW,HCN etc. Firstly, which version do I need and do I also need to install the Easy Connection Server on the phone too? Also, does anyone have a working link as the above versions require logging into a Chinese website (can't understand).
Thanks to anyone that can help!
Easy connected can be extracted from.the ROm..in fact there are several roms that they have extracted for later installation.
Once installed....and connected by usb cable the phone will install the easy connected server and a driver mode app (this one is not necessary but it installs every time you connect and when detects that it is not installed...
I tried with my xperia z3 with 6.0.1 without issues
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
Easy connected can be extracted from.the ROm..in fact there are several roms that they have extracted for later installation.
Once installed....and connected by usb cable the phone will install the easy connected server and a driver mode app (this one is not necessary but it installs every time you connect and when detects that it is not installed...
I tried with my xperia z3 with 6.0.1 without issues
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
Good idea! I managed to find the ROM, extract it, then find it in the OEM.img file.
Can I have a link for the easyconnected app??
Sent from my SM-N9005 using XDA-Developers Legacy app
Tamer amer said:
Can I have a link for the easyconnected app??
Sent from my SM-N9005 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't have a link to the easyconnected app sorry as I extracted it out of the ROM. I since discovered that you can browse to it on my headunit via the apk manager. One thing I learned was the reason this app wasn't working for me in the first place was that my unit has 2 USB ports, and it has to be in the top one to work.
bjt2 said:
I don't have a link to the easyconnected app sorry as I extracted it out of the ROM. I since discovered that you can browse to it on my headunit via the apk manager. One thing I learned was the reason this app wasn't working for me in the first place was that my unit has 2 USB ports, and it has to be in the top one to work.
Click to expand...
Click to collapse
Also my head unit have 2 usb port . But in apk manager I didn't find the easyconnected apk
Tamer amer said:
Also my head unit have 2 usb port . But in apk manager I didn't find the easyconnected apk
Click to expand...
Click to collapse
You have to browse to the mount point OEM, its a different partition, you will have to select it first to browse for it.
bjt2 said:
You have to browse to the mount point OEM, its a different partition, you will have to select it first to browse for it.
Click to expand...
Click to collapse
OK I will try and thanks for your responding to me