DriveDroid with CM10.1 - Galaxy S III Q&A, Help & Troubleshooting

Anyone using CM10.1 managed to use DriveDroid? I'm trying to boot Ubuntu but Windows just say that I need to format the driver, I don't know if it's a CM related, MTP or my issue :cyclops:

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Don't look at what Windows thinks of the disk. Windows doesn't recognize the structure of the disk, so it suggests to format it.
What does matter is whether your bios recognizes the disk as bootable. The structure of the disk is usually not the problem if you downloaded the image from DriveDroid: it is the same as anyone else downloading the image. If booting from your phone does not work it usually has something to do with timing/the software on your phone (ROM/kernel). If you indeed can't boot from your phone, I'd suggest to do the following:
Go to preferences of DriveDroid.
Turn off UMS and turn it back on again.
Reboot your phone.
See whether that helps. It worked for some people, but it doesn't have a 100% successrate.

hipgnose said:
Anyone using CM10.1 managed to use DriveDroid? I'm trying to boot Ubuntu but Windows just say that I need to format the driver, I don't know if it's a CM related, MTP or my issue :cyclops:
Click to expand...
Click to collapse
Same here. Really disappointing it doesn't work. I can't tell you how often I thought about boot an image from my phone. In fact, I think I posted the question on XDA a few years ago.

Hey guys, developer here. A few things that might help:
The ISOs that are in DriveDroids downloadlist are all hybrid. This means they are specially crafted to be compatible with USB as well as CD. This is great, because at the moment Android devices only correctly emulate USB drives.
When selecting such an image, Windows will show it as an USB disk. However, Windows does not recognize the format that is used on the disk, because it's hybrid. Therefore Windows suggests to format the disk with a filesystem that Windows recognizes (FAT or NTFS). Do not do this, it'll just blank out the image, which isn't what you want.
Bioses however should be able to recognize the USB disk as a bootable one.
The USB-disk emulation is what in Android is called UMS (USB Mass Storage). On oldish devices this was used to share the SDcard with the PC. DriveDroid uses the same mechanism, but not on the SDcard, but on files (ISO/IMG). Downside is that this mode isn't by default enabled on modern devices, so you usually have to switch from MTP (the system in use to share SDcard in modern devices) to UMS. Such an option is available in DriveDroids menu. However on some devices this switch does not work correctly atm. I have no idea why, but from others I have heard that you can make the option work on these devices. You'll have to rapidly switch the UMS option on and off and end with UMS being on. It *should* popup on your PC when you have a USB cable plugged in. For others it helped to reboot the phone too, but I'm not too sure why this works.
Hopefully that helps solve the problems.

FrozenCow said:
You'll have to rapidly switch the UMS option on and off and end with UMS being on. It *should* popup on your PC when you have a USB cable plugged in.
Click to expand...
Click to collapse
Funny you suggested this. Last night while trying to make it work (thinking the image didn't download correctly the first time), I did the same thing.

jdgiotta said:
Funny you suggested this. Last night while trying to make it work (thinking the image didn't download correctly the first time), I did the same thing.
Click to expand...
Click to collapse
Oh were you also one of the people who send me a support email about this by any chance? I learned about this from those.
In any case, good to hear another confirmation on the method. It's weird, since I'm not too sure why this works yet (it just enables and disables UMS on my device), but I'll put something in the next version to emulate the same behavior.

FrozenCow said:
Oh were you also one of the people who send me a support email about this by any chance? I learned about this from those.
In any case, good to hear another confirmation on the method. It's weird, since I'm not too sure why this works yet (it just enables and disables UMS on my device), but I'll put something in the next version to emulate the same behavior.
Click to expand...
Click to collapse
No, I didn't send the report. I tried it on a whim, but didn't it work.

Related

Step by Step guide to enabling ADB Connection on your stuborn Nook Tablet

(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Good write up!
The procedure worked fine on my laptop. When I did it on on my home PC I forgot to disable auto-mount and the Nook installed itself as mass storage. I was able to right click -> un-install all the USB Mass Storage entries (with the Nook unplugged), disable auto-mount, plug the Nook back in, and have it show up correctly.
In short, I did not need to use "USBDeView" as I was able to remove the diveres manually. I suppose if you have more than a handful for USB devices (I just have a Mouse, Keyboard, and printer) "USBDeView" might be helpful to determine which drivers to un-install...
The device manager is enough for most people, but there is a somewhat large number of us that are having trouble still. Possibly because of other devices we have installed before. (I dont understand how all the drivers work and I wont pretend to)
Some people have go so far as putting a fresh install on Windows on a partition of a PC.
I had this problem with both my laptop and my desktop, which surprised me. This worked on both the laptop and PC, so hopefully it can help other people.
I cant wait to get my own tablet on the 12, I will take lot of pictures and make this process more user friendly.
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
mtelesha said:
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
Click to expand...
Click to collapse
Did you sort by last time plugged in and delete all of those too? Have you re-checked and then re-un-checked automount/usb debugging and such?
This is interesting, you'll have to come back and let me know if you ever get it working on your PC. Maybe its a good excuse for a nice healthy re-format and reinstall of windows?
l3ft3r1s said:
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
Click to expand...
Click to collapse
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
The_Joe said:
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
Click to expand...
Click to collapse
Yeap, that did the trick, thanks. Drives installed successfully this time, but adb devices still returns nothing.
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
adb error: device offline
This drove me nuts for at least a day. Turns out it is what happens when you are plugged into a USB 3.0 port on your PC side. Find out which USB is 2.0 (Front Panel for ZT Systems), use it and life suddenly gets really good.
The_Joe said:
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
Click to expand...
Click to collapse
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
l3ft3r1s said:
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
Click to expand...
Click to collapse
The problem is sdk uninstall and use ccleaner to clean your PC and registries. Use the drivers provided in this forum
Sent from XDA using one of my Android Toys
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
LadyPenley said:
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Click to expand...
Click to collapse
In the future don't delete your original, just post an edit with the fix. That way when someone else has a similar problem your post can help.
Sent from my BNTV250 using xda premium
mtelesha said:
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
Click to expand...
Click to collapse
Did you find a solution? Thats a problem I sadly dont know how to help with. I would start with:
-Check USBDeview and delete anything android/Nook/usb related. Delete just about everything.
-Restart the device
-Uncheck and recheck the USB Debugging boxes
-Recheck and uncheck the auto-mount box
-Test
-Try a different USB Port
-Try another PC
Thanks but didn't work.
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
The_Joe said:
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Click to expand...
Click to collapse
whitets said:
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
Click to expand...
Click to collapse
I had literally this exact same problem the 6th time I restored and flashed. IF im right, you just need to uncheck then recheck usb debugging.
Let me know if it works!

MTP not working

I don't know what i'm doing wrong, but I can't seem to transfer files to my device for any extended period. I don't know what does it, but at some point, the connection always fails. Windows says the device isn't responding and closes the explorer window or stops copying files, but the device itself says everything is fine.
What am I doing wrong?
You may just need to download some Windows drivers:
http://support.asus.com/download.aspx?SLanguage=en&m=Eee%20Pad%20Transformer%20Prime%20TF201&p=20&s=16&os=32&hashedid=n/a
All you really need is the small USB driver (8 MB). I think that the Global button would be the easiest download. There is also the PC Suite, that includes the USB driver, but not sure you want all of the extra stuff included in that.
tedr108 said:
You may just need to download some Windows drivers:
http://support.asus.com/download.aspx?SLanguage=en&m=Eee%20Pad%20Transformer%20Prime%20TF201&p=20&s=16&os=32&hashedid=n/a
All you really need is the small USB driver (8 MB). I think that the Global button would be the easiest download. There is also the PC Suite, that includes the USB driver, but not sure you want all of the extra stuff included in that.
Click to expand...
Click to collapse
It's installed, but the problem is still presenting.
Well, what are some of the details? What type of files are you transferring? What folder are you copying them into?
Try creating a new folder on your Prime and copying into that folder to see if it makes any difference. Some users have been experiencing issues with the Music and Movie folders. If that is the case for you, try copying into the different folder. If that works, you'll probably just want to delete the old (bad) folder and rename the new one to the old name. Make sure you copy any items out of the old folder before deleting it.
tedr108 said:
Well, what are some of the details? What type of files are you transferring? What folder are you copying them into?
Try creating a new folder on your Prime and copying into that folder to see if it makes any difference. Some users have been experiencing issues with the Music and Movie folders. If that is the case for you, try copying into the different folder. If that works, you'll probably just want to delete the old (bad) folder and rename the new one to the old name. Make sure you copy any items out of the old folder before deleting it.
Click to expand...
Click to collapse
No, that doesn't help either. Any kind of file. ebooks, movies, sideloaded apps, it seems to be completely random, just sometime, out of nowhere, "File cannot be copied, device is not responding, skip or quit?" and sometimes if it's multiple files and I skip the one that DIDN'T work, it keeps going like nothing's wrong.
I did neglect to ask you what version of Windows you are using. But, I'm really not sure there is anything that can be done anyway. I assume you have MTP checked on your Prime settings or you would not even be able to see the Prime on your Windows machine. Anyway, I'm at a loss at this point.
Do you want a workaround that will work with a wi-fi connection?
1) Download Airdroid from the Market to your Prime -- it's free.
2) Run Airdroid on your Prime.
3) You will be given an http address like http://192.168.1.1:8888 and a password.
4) Enter the http address into your internet browser on your PC and enter the password when asked.
5) Click on the Files icon on the web page that shows up on your PC.
6) You will see your Prime's file structure on the left side of the page -- click on the folder that you want to move the files to.
7) Then click on the Import button ... upper right.
8) An new window will appear for importing. Click the Select Files button and any file you select in the browse window will appear in the list and automatically be sent to your Prime.
This is just one of the many things that Airdroid can do.
I have done this many times and find it quite easy and reasonably fast -- not as fast as your wired connection would have been, but at least you can do this.
Yes Your only options at this point is a slow wifi transfer or buy an sdcard to copy files to then transfer in the device it self. This seems very acceptable to some people.
MTP is garbage and has never worked well for me either.
I think this is an android hc/ics problem though.
Maybe once/if we start getting costum roms we will see a usb mass storage option. We will just have to wait for the unlock tool.
Might these filenames contain special characters?
Also, the MTP driver seems to have a hiccup sometimes, check your device manager (Win+R "dvcmgmt.msc"). If there's a little warning at the MTP device, mark it and hit delete or open it and hit Driver Details/Update driver.
Sometimes the queueing of files is also out of sync with the actual transfer to the device. I've had it happen that I wanted to copy a bunch of files, and the device must have reported "tranfer complete" on the first file while it was actually still busy, resulting in a "device busy" error on the next file. When I copied the next file by itself, it worked fine.
MTP is slower than regular USB mass storage because it is designed for hot (un-)plugging, so no delayed writes.
Conect your TFP to your PC once with USB debugging checked and once without being checked. See if drivers DL or update.... Check devise manager to see if drivers are installed if yes reboot computer... Some PCs will not recognize devices without rebooting. Next try a different USB hub and repeat something will work
Sent from my SPH-D710 using xda premium
Ciddy said:
Might these filenames contain special characters?
Also, the MTP driver seems to have a hiccup sometimes, check your device manager (Win+R "dvcmgmt.msc"). If there's a little warning at the MTP device, mark it and hit delete or open it and hit Driver Details/Update driver.
Sometimes the queueing of files is also out of sync with the actual transfer to the device. I've had it happen that I wanted to copy a bunch of files, and the device must have reported "tranfer complete" on the first file while it was actually still busy, resulting in a "device busy" error on the next file. When I copied the next file by itself, it worked fine.
MTP is slower than regular USB mass storage because it is designed for hot (un-)plugging, so no delayed writes.
Click to expand...
Click to collapse
I've noticed that when you change the file name sometimes it works. On my galaxy nexus I have the same problem. But I would transfer files it wouldn't work and then I change the file name and it would work
Lots of good suggestions here that you can try...
However, one more possible work-around that worked for my Ubuntu machine (where MTP is not working, either), in case nothing else works:
I switched to PTP (camera) on my TFP. I could copy just fine. However, this means two steps (a copy then move), because with PTP, I can only copy to the DCIM or Pictures folder.
Well PTP is faster. But it still tells me my camera wont play the file...
tedr108 said:
Lots of good suggestions here that you can try...
However, one more possible work-around that worked for my Ubuntu machine (where MTP is not working, either), in case nothing else works:
I switched to PTP (camera) on my TFP. I could copy just fine. However, this means two steps (a copy then move), because with PTP, I can only copy to the DCIM or Pictures folder.
Click to expand...
Click to collapse
Thanks for that idea. I was going to try that when I got some time but wasn't sure how it would handle it. I can handle just having to movie it to a diff folder once I get it on the prime.
Like the other poster said, can't wait to get a custom rom on this thing.
I ran into this annoying problem yesterday too. At first I thought it was an issue with the drivers on my Windows 7 box, so I went over to my Debian box and installed MTPFS, but no dice. The exact same thing happens - the computer is able to initialize the connection at first, and if you're quick enough you might even be able to copy/delete/move something, but after maybe 30 seconds or so the connection fails - transfers stop, renaming hangs etc. This was the exact same thing that happened on Windows 7 and so I must conclude it must be the TFP itself having issues with MTP. Running ICS IML74K.
MTP works but the date of all files and folders is wrong
tedr108 said:
Lots of good suggestions here that you can try...
However, one more possible work-around that worked for my Ubuntu machine (where MTP is not working, either), in case nothing else works:
I switched to PTP (camera) on my TFP. I could copy just fine. However, this means two steps (a copy then move), because with PTP, I can only copy to the DCIM or Pictures folder.
Click to expand...
Click to collapse
MTP works for me (Ubuntu 11.10). But I have found out, that once the internal storage is mounted in Ubuntu, the date of all files and folders are set to 1970-01-01.
Actually before, short after I had activated the Prime, I realised that the date was also wrong. I'm not sure now, but probably the same 1970-01-01. Then I adjusted the date and the upgrade to ICS went flawlessly.
Now I start thinking that this wrong date could be one of the reasons for many problems in TF Prime.
Does anybody have the same problem and know a solution?
I read in another forum when i was trying to get mtp to work on my nexus s that if you install media player 10 it can solve the issue of mtp not working in windows xp. Not sure if this applies to windows 7 though as i thought windows 7 was supposed to be able to use mtp out of the box.
-RioT- said:
Yes Your only options at this point is a slow wifi transfer or buy an sdcard to copy files to then transfer in the device it self. This seems very acceptable to some people.
MTP is garbage and has never worked well for me either.
Click to expand...
Click to collapse
On my Galaxy S2 MTP works like a charm, so it's not MTP in general. Maybe it's a bad USB cable, connector probs or Windows acts up.
It's May, and MTP is still garbage.

[Q] Mount to Computer (Linux)

I've been trying to find a way to mount my DNA to my linux work machine, but for the life of me I can't figure it out. All searches of the net yield nothing successfully. I assume it's because the phone keeps connecting as PTP, when I really need to have it in MTP (I miss mass usb storage;( ). Has anyone had luck connecting theirs to their linux machine. I just wanna transfer stuff from my old phone's sd card.
djak250 said:
I've been trying to find a way to mount my DNA to my linux work machine, but for the life of me I can't figure it out. All searches of the net yield nothing successfully. I assume it's because the phone keeps connecting as PTP, when I really need to have it in MTP (I miss mass usb storage;( ). Has anyone had luck connecting theirs to their linux machine. I just wanna transfer stuff from my old phone's sd card.
Click to expand...
Click to collapse
You need libraries that are able to access the MTP device. I don't have anything to test on right now, but this looks promising:
slackbuilds.org/repository/13.37/multimedia/mtpfs/
found this too:
wiki.archlinux.org/index.php/MTP
(sorry, I can't post real URLs because I haven't posted enough... just add the usual prefix to this.)
weasel0x00 said:
You need libraries that are able to access the MTP device. I don't have anything to test on right now, but this looks promising:
slackbuilds.org/repository/13.37/multimedia/mtpfs/
found this too:
wiki.archlinux.org/index.php/MTP
(sorry, I can't post real URLs because I haven't posted enough... just add the usual prefix to this.)
Click to expand...
Click to collapse
That doesn't seem to be the problem. I can't switch it to mtp mode. It shows up mounted as a camera, but then I get an error saying that it can't be unlocked or something like that. That was what I meant in my original post that I think it's still in PTP mode, which is why your suggested method didn't work for me. Thanks though. There should really be more support on linux for this if Google is forcing people to use MTP transfer now instead of UMS, which was universally supported... and better in my opinion.

[Q] Rooted P7510 - Not being recognized by PC

Hey there,
Here is a list of what I have before I get started.
Samsung Galaxy Tab 10.1 Wifi (P7510)
Android Version - 3.2
Kernel Version - [email protected]#1
Build Number - INFAMOUS TAB 0.1 P7510UEKMM
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
I bought this tablet from a friend who rooted and flashed with the INFAMOUS mod.
I have searched all over the web for an answer and cant find something for this case specifically.
Each time I plug in my tab, my PC tells me that the Hardware ID is missing.
I can see the tablet in my Devices and Printers (displayed as SAMSUNG_android) as well as in my Device Manager. In device manager it says the drivers are up to date and functioning.
What have I tried?
USB Debugging (On and Off)
Clearing cache via recovery mode
Updating drivers via W7 and KIES via Samsung
I have tried following a few threads on installing the KIES software without internet connectivity. However I would rather not use the KIES Software anyway as it is kind of garbage.
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Can anyone point me in the direction of help and me being able to enjoy this tablet?
I hope I have provided enough information. I am a pretty techy person and I understand how to do all of this but it seems like I am missing something really big.
Something to take note of, whenever the tab is plugged in (PC or Wall) there is a red x over the battery symbol and the tab charges very slowly.
Cheers
B
Snugglebutt said:
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
...
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Click to expand...
Click to collapse
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
hope this help
FIXED
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Click to expand...
Click to collapse
Ahhh ha! As soon as I uninstalled the driver that windows found and used the Google Driver that came along with the Android SDK, the tablet was recognized. Alas, I can finally use this tablet.
In the end it was as simple as a driver error, I spent a very long time searching last night and now I just feel silly.
The tablet still shows the red X over the battery symbol, whether I have MTP with USB Debugging on or off. I guess this can be avoided with certain ROMS. Anybody know of a ROM that avoids this?
Thank you all for your immediate responses!
B
Tid bit of info
H. Ess said:
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
Click to expand...
Click to collapse
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
Click to expand...
Click to collapse
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Snugglebutt said:
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Click to expand...
Click to collapse
For honeycomb and many others, debugging is always there. Under the storage option, you have an Additional Settings button usually and it should be present in there. I was always running3.2 until like a couple days ago so surprised its not there. Oh well problem solved lol
I'm having a similar problem with my tab not being recognised by my pc (win7 64) or in kies. It was originally an M380W (Korean) model, which I updated to a P7510. That all went fine, and the tablet works perfectly, except for the fact that my pc no longer sees it when it's plugged in. I tried uninstalling and reinstalling the drivers, but no dice. I'm going to see if adb works.

[Q] Is there any ROM/APP wich enables UMS on this smartphone?

Hi,
MTP and PTP are full of problems... so I want to have the old reliable USB Massive Storage (UMS) enabled in this phone, Is there any ROM with this feature?
I'm with stock and I would prefer not to unlock the boot loader unless I can get that feature with a ROM.
I tried this app with no success
I want any PC to detect my phone as a USB flashdrive containing only the sdcard files, not any partitions like system or data or such.
thanks
hitokiri_jaguar said:
Hi,
MTP and PTP are full of problems... so I want to have the old reliable USB Massive Storage (UMS) enabled in this phone, Is there any ROM with this feature?
I'm with stock and I would prefer not to unlock the boot loader unless I can get that feature with a ROM.
I tried this app with no success
thanks
Click to expand...
Click to collapse
Nope. UMS is dead as far as Google is concerned.
what do you mean by that? I know some ICS ROMs with UMS (but for other phones) so it's no dead dead dead and doing a quick search there are some people using ums un Jelly bean
What I mean is, UMS support isn't the way google wants people to do things.
It's a kludge when google wants phone memory not be segmented for apps vs media and such.
I've found MTP works very well on this phone compared to others i've owned.
It's a partitioning issue on any phone that comes with ICS natively.
mmm may be I wasn't clear about that, sorry,
I only want any PC to detect my phone as a USB flashdrive containing only the sdcard files, not any partitions like system or data or such.
And we are saying it isn't going to happen. What trouble are you having with mtp? Maybe we can help.
Ok, thanks, my problem is the following
I have 3 windows machines and in all of them the following happened
> I connected the LGOG to the pc and selected the pc software option in the phone
> Installed the LG software
> The LG software Drive disappeared from "Computer" (as expected I suppose)
> The phone-drive never showed in Computer
> I unplugged the phone and plugged again and selected MTP
> The phone-drive never showed in Computer either
In one of the PCs I got an error while installing the MTP driver, don't know how to solve that, if I try to reinstall the LG software the LG software driver disappears
Also I can't copy files to my phone if I don´t have Administrative access to the PC... that's main the reason I want UMS
Uh oh.
So, if I understand correctly, I'm going to need to install CM in order to use my phone as a thumbdrive.
While I have no problems using MTP, the INSANELY SLOW TRANSFERS are basically going to force me to find another solution.
Great phone, but 2MB/sec on a standard USB 2.0 port just isn't working.
More research, it appears that I'll need to install an FTP server on my phone, or use a wireless data sharing app (sadly not possible in my case as my wireless network is firewall-external to my wired one).

Categories

Resources