Hi guys,
I tried to backup the efs of my device but it always fails.
If I try it with the toolbox 2.0 error messages: protocol error (status red) more then one device and emulator" shows up
If I try it with the N7100 EFS Backup / Restore tool it shows up the same error messages.
If I try EFS Pro 1.12.6 it also fails and shows error message that I have no root acces on my device, but SuperSU is activated.
I plug the device with developer usb debugging activated to my PC. Also as PTP connection, not in mass storage mode.
My OS is Win 7 64 Bit and I installed Samsungs USB drivers from the Toolkit.
Can anyone suggest a solution?
Kind regards
EDIT: I used a virtual machine with windows xp and it worked out. I also figured out my fault. I didnt had to plug it as camera . I trief it again on my primary OS (Win 7 64 bit) but it doenst work on it for, only on xp.
Thread can be closed as it is solved.
Glad you figured it out, but you could have just used root explorer or similar and copied the efs folder from root directory.
Sent from my GT-N7100 using Tapatalk 2
Related
Hello
I have a rooted note 2 and the mtp drivers wont install, anyone else have this problem?
tyfting said:
Hello
I have a rooted note 2 and the mtp drivers wont install, anyone else have this problem?
Click to expand...
Click to collapse
Reinstall the drivers again in Kies, reboot the pc and try again mate. Or install these driver`s https://www.dropbox.com/s/qvvtkwaqc6uqt4p/SAMSUNG_USB_Driver_for_Mobile_Phones.exe and reboot.
How about for mac? Its no working with the android file transfer i have to put my sdcard out everytime i want to transfer big files
Envoyé depuis mon GT-N7100 avec Tapatalk
Done that but still not working.
tyfting said:
Done that but still not working.
Click to expand...
Click to collapse
Well appearently they are not quite installed correctly, or it would work I would uninstall all the drivers and Kies if you have it installed, reboot and connect your phone and force Windows to install the drivers.
Still fails
i know what we have to do to get mtp drivers working
And that is? factory reset phone?
Remove files wpdmtp.inf and wpdmtp.PNF from the folder Windows/inf/ make sure u do a backup
If this works dont forget to press thanks
Still not working
im having the same issues here
Me too...Installation of MTP failed...
I have tried almost everything.And i said ''almost'' cause the answer is somewhere around...
So, i used fresh kies installation - failed
I unistalled Kies and drivers, reboot, install only drivers - failed
I unistalled drivers, reboot, connect my phone to find MTP auto - failed
I reinstall all previous for 2nd time - failed
I install microsoft MTP drivers - failed
I tried in all usb ports in my PC - failed
I tried previous samsung drivers - failed
The last solution is to format PC but i want to avoid this if its possible...
If someone google the problem can find lot of people with this but not a clearly answer.We are not alone in this universe!!!
If someone, master of windows 7 (64) can help, will be my hero!!!!!!!
I ended up factory restoring my phone and the it finally works, sad but true it seems to be the only fix.
tyfting said:
I ended up factory restoring my phone and the it finally works, sad but true it seems to be the only fix.
Click to expand...
Click to collapse
Oh man ... I had MTP working flawlessly yesterday ... but today I can't get it to work. Bone stock SGH-i317 (the AT&T version of the Galaxy Note 2)
In Windows Device manager:
MTP USB Device:
"This device cannot start. (Code 10)"
Just using stock Windows 7 x64 bit drivers -- had no Samsung software installed at all. And then on the phone sometimes after unplugging from the phone "MTP" force closes on the phone. Maybe if I clear Media Storage on the phone.... clearly this is a phone issue and not something on my PC>
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
Yes, that worked. Go to Settings -> Application -> All and find "Media Storage."
Then hit clear data. MTP will work again.
You will need to rebuild the database, which will happen automatically. May take a while depending on how much stuff you have on the phone. There are tools on the Play store to help you look at the status of this process.
I had this problem from day 1. And no matter what I do I couldnt get it to work, I think I tried every solutions on the net already. I reinstall windows and been working since. Of course that's the last resource if you cant get it to work.
Make sure you haven't froze the "mtp application"in titanium or a similar program.
I couldn't get my note connected to my PC until I unfroze that app.
Sent from my Galaxy Note 2 using Tapatalk 2
I am having this issue with all drives, I have windows 8 MTP and PTP both won't work. My computer at home and work get the exact same issue.
eliashadow said:
Me too...Installation of MTP failed...
I have tried almost everything.And i said ''almost'' cause the answer is somewhere around...
So, i used fresh kies installation - failed
I unistalled Kies and drivers, reboot, install only drivers - failed
I unistalled drivers, reboot, connect my phone to find MTP auto - failed
I reinstall all previous for 2nd time - failed
I install microsoft MTP drivers - failed
I tried in all usb ports in my PC - failed
I tried previous samsung drivers - failed
The last solution is to format PC but i want to avoid this if its possible...
If someone google the problem can find lot of people with this but not a clearly answer.We are not alone in this universe!!!
If someone, master of windows 7 (64) can help, will be my hero!!!!!!!
Click to expand...
Click to collapse
Try restarting your phone. I had the same issues with my Galaxy Note, Galaxy Tab 10.1, and Galaxy Note II. It should work. It did for me
mentalcase87 said:
I am having this issue with all drives, I have windows 8 MTP and PTP both won't work. My computer at home and work get the exact same issue.
Click to expand...
Click to collapse
Don't factory default your phone.
Like in my post above, just go to Applications -> All and select 'Media Storage' ... Hit clear data. Problem solved.
I just had this happen again -- and this fix worked perfectly -- again.
MTP Driver Fails
Same problem here, Stock Rom.
Tried all recommendations above and still mtp fails
I had a HARD time trying to get the GS3 to connect to my PC (like a lot of other peps)
Here is my solution:
Update the pc completely using Microsoft Updates.
Download the following:[URL=http://depositfiles.com/files/jfh66znxv]http://depositfiles.com/files/jfh66znxv[/URL]
Un rar and copy the INF files (2) to your windows inf folder. I found that 1 of my original files (Microsoft installed) was actually the problem!
Install the Snapdragon Toolkit and install the Samsung driver using that software. (First option)
I already had done it via manual installs a number of times, but they never worked. This install using the toolkit worked.
(I only used it to install the Samsung Drivers)
Rebooted the PC and ran the toolkit again and saw the serial number in the ADB window, confirming a connection!
Rebooted the pc and connected the SG3 via the usb cable and it showed the files after a short moment!
All is Good!
Hope this helps someone make theirs work and alleviate all the aggrivation.
BTW:
There was not any problem with the Samsung software, It was the PC that had the problem!
I had that Samsung MTP error and the INF file installaion actually fixed that problem, so I included them in the file to download.
If this works for you, plz add a tag to this thread so that others will know this works.
Anyone know about the issues with connecting to Mac? I cannot connect with MTP or ptp only easy ums app works but I'd like to mount both of the SD cards
Sent from my SGH-T999 using xda premium
Okay, so I'm trying to copy files from my PC to my Nexus 7 FHD. First tried on a Windows 8.1 PC and when I plug in the N7, it installs the MTP drivers (driver date is 2006 from Microsoft). Shows up in my file explorer and I try to copy some photos but after about 5-10 seconds, it will just freeze and basically file explorer crashes.
Read another thread about MTP driver issue (http://forum.xda-developers.com/showthread.php?t=2380978) but none of that helped. Uninstalled the driver, restart, install new driver. No matter what the MTP driver is the same.
Read somewhere else that it could be a Windows 8 issue so tried on a Windows 7 laptop and same result.
No matter what, file transfers over USB wont work.
So, is this a Nexus 7 issue as a whole (as I had no issue with my N4) or just my particular device as if so, I'll return it for another one.
Any help would be appreciated.
Cheers.
EDIT: Noticed that I'm getting an error on the N7 that I hadn't noticed: Unfortunately, the process android.process.media has stopped. Looks like I might need to reinstall the OS from an image to fix it.
Hi guys,
I flashed the cm12 beta 2 recently and afterwords mobile was not recognized by pc. I tried reinstalling the drivers and changing rom, reverting back to kitkat.. but it was of no use. Now i have upgraded from windows 7 ultimate to windows 8 64 bit. I installed the drivers, Im getting "Unable to start the device(code 10)" . Even now im unable to connect to pc via usb and everytime i connect it says "Usb not recognized" . Please help me fix this
Thanks
same issue I am on Windows 8.1 x64bit.
marcusflint said:
Hi guys,
I flashed the cm12 beta 2 recently and afterwords mobile was not recognized by pc. I tried reinstalling the drivers and changing rom, reverting back to kitkat.. but it was of no use. Now i have upgraded from windows 7 ultimate to windows 8 64 bit. I installed the drivers, Im getting "Unable to start the device(code 10)" . Even now im unable to connect to pc via usb and everytime i connect it says "Usb not recognized" . Please help me fix this
Thanks
Click to expand...
Click to collapse
First make sure you have usb debugging off, in your devixe.
I found Micromax A1 doesn't work with Windows 8.1 x64 so I reverted back to Windows 7 x64 now it works fine.
marcusflint said:
Hi guys,
I flashed the cm12 beta 2 recently and afterwords mobile was not recognized by pc. I tried reinstalling the drivers and changing rom, reverting back to kitkat.. but it was of no use. Now i have upgraded from windows 7 ultimate to windows 8 64 bit. I installed the drivers, Im getting "Unable to start the device(code 10)" . Even now im unable to connect to pc via usb and everytime i connect it says "Usb not recognized" . Please help me fix this
Thanks
Click to expand...
Click to collapse
Hey there!
I'm also using cm12 beta 2
Windows won't recognize the device untill you do this:
Disable usb debugging from developer options. The phone will reboot. Then enable the
Usb debugging again. Now connect your device to pc and voila !
+I am also using windows 8 64 bit. So I don't think it is a compatibility issue.
Hello everybody
My main question is that if its possible to root the device without using an usb cable (typical flashing twrp's recovery with adb and then flashing the magisk zip in the recovery).
My phone cant be recognized by any pc, it gives me a descriptor error 43 on windows 10/8 in 3 differents pc's and changed many times the cable. Tried every thing on the internet about fixing the error 43 descriptor error. I need urgently the root because i have backup all my data with titanium backup before resetting the phone into factory due to some issues. After the reset i lost the root and the recovery mod so i cant use the titanium backup to restore all my data.
Any help will be appreciated.
Blackfox1010 said:
Hello everybody
My main question is that if its possible to root the device without using an usb cable (typical flashing twrp's recovery with adb and then flashing the magisk zip in the recovery).
My phone cant be recognized by any pc, it gives me a descriptor error 43 on windows 10/8 in 3 differents pc's and changed many times the cable. Tried every thing on the internet about fixing the error 43 descriptor error. I need urgently the root because i have backup all my data with titanium backup before resetting the phone into factory due to some issues. After the reset i lost the root and the recovery mod so i cant use the titanium backup to restore all my data.
Any help will be appreciated.
Click to expand...
Click to collapse
Use USB hub or win 7..
You can even find registry patch for win 10 on xda.
And use latest ADB/fastboot version.
Good luck and stay safe!
drnightshadow said:
Use USB hub or win 7..
You can even find registry patch for win 10 on xda.
And use latest ADB/fastboot version.
Good luck and stay safe!
Click to expand...
Click to collapse
Just tried an usb hub and it gives the same error. It must be something wrong about the phone. I ll tried later with win7, but i dont think it would be the problem since i even tried right now with linux mint and macOS and got a similiar error.
I always use the latest adb from here xda, any other tip to try with? If its possible to restore the backup file from titanium backup without root i dont really need the root tbh.
Blackfox1010 said:
Just tried an usb hub and it gives the same error. It must be something wrong about the phone. I ll tried later with win7, but i dont think it would be the problem since i even tried right now with linux mint and macOS and got a similiar error.
I always use the latest adb from here xda, any other tip to try with? If its possible to restore the backup file from titanium backup without root i dont really need the root tbh.
Click to expand...
Click to collapse
Titanium backup needs root or it will fail even froze the phone. Root is needed to flash.. you cab try flashify to flash twrp, but you can brick your device. I wouldn't try that.. try on win7 first, check drivers, version adb/fastboot , etc.
Check the official MIUI forum for drivers, adb, etc...
Good luck and stay safe!
drnightshadow said:
Use USB hub or win 7..
You can even find registry patch for win 10 on xda.
And use latest ADB/fastboot version.
Good luck and stay safe!
Click to expand...
Click to collapse
drnightshadow said:
Titanium backup needs root or it will fail even froze the phone. Root is needed to flash.. you can try flashify to flash twrp, but you can brick your device. I wouldn't try that.. try on win7 first, check drivers, version adb/fastboot , etc.
Check the official MIUI forum for drivers, adb, etc...
Good luck and stay safe!
Click to expand...
Click to collapse
Tried win7 already, got similar error, so, im almost sure that this descriptor error is something about the phone itself.
i guess i gonna buy a xiaomi mi 10 lite 5g for 200 bucks before this bf ends, root it and hope the data can be restored without too much issues.
Thanks for your time sir
Blackfox1010 said:
Tried win7 already, got similar error, so, im almost sure that this descriptor error is something about the phone itself.
i guess i gonna buy a xiaomi mi 10 lite 5g for 200 bucks before this bf ends, root it and hope the data can be restored without too much issues.
Thanks for your time sir
Click to expand...
Click to collapse
No problem, that's what XDA is here to help community.
Good luck and stay safe!
[/QUOTE]
Blackfox1010 said:
Hello everybody
My main question is that if its possible to root the device without using an usb cable (typical flashing twrp's recovery with adb and then flashing the magisk zip in the recovery).
My phone cant be recognized by any pc, it gives me a descriptor error 43 on windows 10/8 in 3 differents pc's and changed many times the cable. Tried every thing on the internet about fixing the error 43 descriptor error. I need urgently the root because i have backup all my data with titanium backup before resetting the phone into factory due to some issues. After the reset i lost the root and the recovery mod so i cant use the titanium backup to restore all my data.
Any help will be appreciated.
Click to expand...
Click to collapse
hallo there.. this is first time i comment on xda,sorry my bad english..
i have same problem with u,
can't connect to any pc afther installing update to miui 11
i try on win 7/10 on diferrent pc but can't connect to.
and then i try to open back case and release pcb port charging and reheat with air gun
250/2 for 10minute, and whoolaa its working again..
i don't know wheres the problem but it work on my phone
good luck and stay safe..