I'm running "Megatron" 1.0.4 on my Transformer. However this was occurring with the predecessor CM9 build (before the author renamed to it "Megatron"). I had switched from the Stock asus rom to CM9 a while ago, I was running the 3/29 build of CM9 (as mentioned above), which turned into Megatron.
I use adb to push and pull files to/from my tablet, as i find MTP to be utterly useless. I also use adb for shell access and other things when i'm tinkering with Android.
adb was working perfectly, On the 3/29 build of CM9. I was quite happy with 3/29, which is why i ran it for the entire month of april, without updating to "Megatron". However, one day, adb suddently stopped detecting my device. Restarting the adb server doesnt help, i've tried doing things like wiping cache on my device, nothing helps. I updated to Megatron 1.0.4 to see if that would help (thinking it was a software thing), with no data wipe, the tablet is again working perfectly except for the adb issue.
When i connect my tablet to my pc over its USB cable, the notification area disaplsys that usb debugging is enabled, but i still can't detect it with adb.
So, how can i continue to troubleshoot this? Is there some sort of debugging log i can view? Or enable some verbose mode?
Any suggestions would be great. Thanks!
Just did a full wipe, still, adb is unable to see my device.
Some extra info.
My PC is Linux, Fedora 16.
adb version:
$ adb version
Android Debug Bridge version 1.0.26
I havent updated it in a bit, but as stated earlier, neither it, nor the tablet's config changed when this stopped working.
Related
I've tinkered with Android development a few months ago. I used the Android SDK v12 in Eclipse. Stuff worked then, on two separate machines. One Debian Squeeze/AMD64, one Ubuntu 10.04/i386. I did not reinstall/wipe/"repair"/mess up anything on these two PCs, promise.
I was offered an OTA firmware upgrade for my Xperia Neo (MT15i) a month or so ago. I accepted and got Android version 2.3.4 now (build number 4.0.1.A.0.283).
Now when I plug it in, the phone immediately pops up the "USB Debugging connected" notification, as it should be. Because that's certainly enabled.
But I can't select the phone for running my in-development apps from within Eclipse anymore. The phone does show up in the device chooser, but it's all question marks and N/A and I can't select it as a target. Picture attached.
Console says
Code:
07:53:20 E/DDMS: insufficient permissions for device
com.android.ddmlib.AdbCommandRejectedException: insufficient permissions for device
at com.android.ddmlib.AdbHelper.setDevice(AdbHelper.java:736)
Things I've tried after discovering this problem include rebooting my phone a dozen times with different USB Debugging settings, rebooting it while plugged into the development machine, rebooting the development machine, toggling the option while plugged in, ending processes on the phone I thought might interfere (SE LiveWare helper, SE USB extensions ...), running 'android update adb', upgrading to the Android SDK r13, redownloading all the SDK platforms and platform tools and so on and so forth. Nothing changed. The DDMS keeps looking as pictured, and the error message stayed the same, too.
What to try next? I really don't want to have to root my phone. USB debugging is supposed to (and did) work on stock firmware. Even if I wanted to root, it does seem complicated and risky with this model/OS version.
PS: Yeah, I've tried to post this to Xperia Neo=>Android Development but the forum software wouldn't let me.
Solved it.
Had to do this:
Code:
cd andorid-sdk-linux_x86/platform-tools
sudo ./adb kill-server
sudo ./adb start-server
sudo ./adb devices
DDMS and Eclipse deployment now work again, running either as normal user (no root privileges).
Found on Google groups, thread id f85a795644e65b59. Can't link because I'm spam, apparently
UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/
well I see you fixed it. did you get adb going?
Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk
are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.
Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone
Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
On Mac try sudo adb whatever
Always with sudo
Sent from my MB865 using xda app-developers app
xxDriveNxx said:
Hey everyone.
So I updated my Atrix 2 to the ICS leak earlier today, and can't for the life of me get it to show up in ADB.
What I've done:
1) Tried on Windows (7) and Mac (10.7) using the SDK and downloaded versions of ADB.
2) Installed different Moto drivers on the PC. Ones that I found via a Google search, and the ones on the phone when mounted.
3) Toggled USB Debugging on and off 100+ times, and checked through all the settings.
4) Tried different mount modes- MTP, PTP, and Mass Storage, all while toggling USB debugging.
5) Tried adb kill-server, adb start-server, adb devices, adb usb, adb wait-for-device way too many times.
6) Tried different USB ports and different cables on both computers
7) Tested my Galaxy Nexus (verizon) which was detected by ADB on both setups with no trouble
8) Booted into Fastboot and tried ADB, but no luck.
At this point I'm ready to smack my head against the wall. Why in the world won't the phone get detected by ADB?
Any advice or help is greatly appreciated!
Click to expand...
Click to collapse
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
cogeary said:
I had the same problem initially as well. I did some research and found a thread on the Moto support forum in which people with the official Razr ICS had the same problem. What finally fixed it for me was:
-Uninstall all drivers for your A2, reboot
-Install THESE drivers, reboot
-Factory reset (Settings->Privacy->Factory Reset, or something like that). Yes I know it's annoying but it's necessary.
-Once your phone reboots, just sign into google. Don't uninstall any apps or do anything like that. Don't enable USB debugging either.
-Connect for all 3 different connection modes. Wait for the drivers to download each time. If a driver fails to download, then uninstall it (not the MotoHelper), reboot your computer, enable the installation of unknown sources on your phone, then repeat this step.
-Once you have all those drivers installed, time to reinstall them with ADB! Enable USB debugging and repeat the previous step
-Once all your drivers are installed, reboot for good measure. But you should be good to do whatever you want now.
Hope this helps. I know it's a pretty roundabout way, but it works :\.
Click to expand...
Click to collapse
I guess I'll have to give the factory wipe a shot tonight. I was really hoping it wouldn't come to that since I can't use Titanium Backup due to lack of root.
all i did was have my phone plugged in while i was installing the drivers. but i did have to download the ones from your post.
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
kousik said:
I followed the steps as above except the factory reset part (as that's a painful experience) but no joy. After ICS OTA upgrade, no adb for me. Looks like I'll bite the bullet and do a factory reset finally.
Before that I'll wait if anyone can post an easier workaround here. I have a 32-bit windows vista. (And a Ubuntu virtual machine on vmplayer)
ADDED Finally `Factory reset' had to be done and that did the trick. Without factory reset, the phone will not present itself as a ADB interface - hence ADB driver won't load - hence ADB will not detect it. So I don't know if all the driver uninstall/install/reboot in 3 modes ritual is necessary ... if you have all the drivers, just factory reset/wipe data and the phone shows up in adb.
Click to expand...
Click to collapse
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Bob G said:
I had the same problem and did a factory reset yesterday. It worked fine, so I re-rooted.
But that was yesterday. Now today, adb will not connect again. Something more is going on here. I suspect it is related to the fact that I did the OTA update from ATT without first un-rooting or doing a factory reset. I also had added files to system memory (ringtones - which are still there).
EDIT: Sorry, I spoke too soon. One thing I hadn't done was to "Connect for all 3 different connection modes." I had only connected in Mass Storage and Media Device modes, so I connected in "Camera (PTP)" mode, allowed the drivers to install on my PC, and then adb started working again (in Camera or Media Device modes, but still not in Mass Storage Mode).
Click to expand...
Click to collapse
FYI adb will not work in mass storage mode.adb needs the phone memory and other access which are not there when you connect your phone in mass storage where it acts merely as a card reader
Sent from my Atrix2 Stock ICS Leak#2 Rooted,Deodexed,With Google Now...
Just in case anyone else was on the fence about doing this: I had tried a million things (trying different computers, different USB cables, installing and uninstalling different drivers, editing driver inf files, editing adb_usb.ini, etc) for several days and nothing worked. I was skeptical about the factory reset helping, but now that I did it I can finally connect to my phone. Yay!
Hi everyone, I've been doing a good bit of googling and found nothing yet, so if this has been asked before I'm very sorry but I haven't yet seen anyone on the forum with the exact same issue. I actually updated to JB OTA when I first got the device in Canada (US version), when I got back to the UK I decided to root, but then found out that you can't on JB, luckily I managed to downgrade to ICS V9.4.5.30 downloaded from the ASUS website! I was not able to downgrade to an earlier version however, stock recovery wouldn't allow it so NVFLASH root method is out the window... Now I would prefer not to unlock my bootloader for now.
When running debugfs.bin 1 click root method, on my desktop (not run as admin) it says:
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
*daemon started successfully *
'find" is not a recognized as an internal or external command, operable program or batch file.
Less than half a second later it just closes down.
When run as admin, it does the same thing and instead of closing down it goes back to the first screen where you can select what method you want to use.
On my netbook it runs and just stops at daemon started successfully, the tablet has no response and debugfs just stays on that screen till I close it down.
Both my computers have all the correct drivers and the latest version of debugfs running, both are windows 7 Ultimate 64-bit.
Please help me as my Infinity is just sitting around doing nothing as when I downgraded to ICS all 190 apps I installed were wiped too, and obviously there's no point me reinstalling any apps till I get this bad boy rooted...
Many thanks in advance!
Make sure you're connecting to a USB 2.0 port, not 3.0, on your computer.
Try not to use any intervening USB hub.
Try to make sure that you're using the back ports on a desktop machine as sometimes the front ports and be a bit sketchy.
Reboot both tablet and computer before starting, and as always, make sure the tablet has USB debugging enabled.
only my netbook has usb 3.0 and I used the 2.0 port, I will now try the back ports of my desktop, I didn't use any extensions or usb hubs, I have debugging and unknown sources checked. I have tried the restarting already, which I'll do right now again... thanks though..
Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?
Android SDK and Java DK were not installed, just installed them still exactly the same issue, haven't rebooted since installing them though
Is there a way I could use Linux to root, as I do have Linux Mint running?
johnlgalt said:
Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?
Click to expand...
Click to collapse
I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link
johnlgalt said:
I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link
Click to expand...
Click to collapse
Thanks so much anyway! I've already tried that file, it's exactly the same
Yeah, it looked very similar, but it included more things in the actual Download like the drivers.
Not sure why it is not working - can you run those three commands in a command prompt window and see what you get?
well they say 3's a magic number, computer number 3 worked! For some reason something on my desktop and netbook was causing the root to fail, now I'm updating to jb ota... Thanks for the quick responses otherwise I would have assumed the problem was with the tablet and not my machines...
Glad you got it working. Quite possibly an antivirus program, firewall, or other such problem.
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
I'm in a similar situation except I'm not rooted or unlocked. I've tried just about all the steps you've mentioned w/ no luck. I've even tried to three different PCs running XP, Vista, and 7 and get the same result. What makes the situation even worse is my brand new 32GB microSD card won't read on my desktop as well.
m000se said:
Hi
Some background. Like many, I bought a TF700T and like a fool installed the OTA update to JB. I then downgraded, rooted in .30, then upgraded again and flashed SU to keep root in JB. I am now, therefore, running the stock OTA JB ROM, rooted. My bootloader is also unlocked.
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
I want to get files on and off the *internal* storage (I don't have an external sdcard)
Things i have tried:
- Using a different USB port
- Using one of the USB ports on the back of the machine, instead of the front ones
- Uninstalling the MTP drivers
- Using the ASUS drivers from the website
- Cleaning out all my old unconnected USB devices (show devmgr_unconnected_devices=1 or whatever) and uninstalling all THOSE drivers
- Cleaning out with USBDeview
- Fresh install of the OTA ROM, after a data wipe/factory reset and wiping cache and dalvik
The only things I haven't tried are a new USB cable (damn you ASUS and your proprietary connector), and a clean install of Windows (major ballache).
Any ideas about what I could do to sort this would be greatly appreciated.
Since I only want to be able to move files on and off the device, I tried a workaround. I tried mounting the sdcard (internal) in windows manually through adb but the command I used to use on my old S2 through adb shell (echo dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file) but it errors with No such path or similar. I'm unsure if the mount points are different (I guess they will be, can anyone help with telling me what the mount point for the internal emmc is on the tf700?)
Really hope someone will be able to help me!
Thanks in advance guys
Click to expand...
Click to collapse
First check make sure you have your "USB debug" and "Unknow software" checked in settings. Then go here and install the pda software for your windows. Once installed, it will installed all the driver for your tab automatically. You don't need to use the software, you can uninstall it later, but the driver will stay.
http://junefabrics.com/android/download.php
I haven't picked up a TF700 yet (out of stock locally), so these are just general suggestions...
From adb, shell into the OS (adb shell) and list the directories to try and determine their structure. If the device is booted, the internal SD should already be mounted.
I would start by looking for the following folders:
/sdcard
/mnt/sdcard
/data/media
m000se said:
Hi
Initially after this, plugging the TF700 into USb on Windows 7 (x64) worked fine - the device popped up as a Media Device and I could transfer files on and off it with ease. Now, without changing anything on either end, Windows is refusing to play. It tries to install MTP drivers but fails. If I boot the device in either CWM or Fastboot it connects fine (with adb and fastboot, respectively).
Click to expand...
Click to collapse
I had the same problem getting MTP to work on old XP machine. The following worked for me...see post #12
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html
Thanks for the replies, everyone. I installed PDANet and was initially hopeful once the drivers started installing. Sadly, Windows still doesn't see my device.
adb shell-ing into the device --> mounts
This lists /dev/fuse as the internal storage. I can't echo this to /sys/devices/usb_mass_storage/lun0/file because when I do it returns "No such file or directory"
The solution posted as working on XP machines doesn't work either.
This is seriously annoying. I'm tempted to just give in and get myself a 32GB SDHC and card reader and just use that instead - at least that way I can move the files across with Root Explorer or something...