Ron Khan asks:
I am using a Galaxy W (GT-I8150) and I am trying to access my internal SD to transfer some huge game files. However, I can only access my external SD when I plug in the USB cable to my computer. Thus, I had no choice but to use AirDroid, which is very time-wasting compared to just dragging and dropping.
Before I rooted my phone and flashed it with CM9, it could access both internal SD and external SD. However now, it can’t. I can access both the SD Card and the EMMC from the phone.
Any help here? I just want to access my internal storage using my com. Thanks!
Browser: 2.3.6 (Flashed with CM9, 4.0.4)
System: Android
Tagged: android, android issue, hardware issue, internal drive, mobile issue, root phone, sd card
System: Android
Tagged: android, android issue, hardware issue, internal drive, mobile issue, root phone, sd card
4 Answers -
Henry Lahman
July 31, 2012You need to make sure it’s mounted read/write
It is… BTW what is R/O?
August 2, 2012Isn’t that read only?
August 3, 2012R/O Read Only
W/O Write Only
R/W Read & Write
ha14
July 31, 2012possible this solution here can help?
http://www.thriveforums.org/forum/toshiba-thrive-general-discussions/5032-simple-solution-external-sdcard-write-access-android-3-2-if-youre-rooted.html
Root # All Data2SD card.
https://play.google.com/store/apps/details?id=rappsd.v1&hl=en
I will try your method. Thanks…
August 1, 2012I cant find platform.xml. Sorry
August 2, 2012Kannon Y
August 1, 2012My first guess was that you don’t have the correct permissions to access your internal memory. This is often by design. Internal memory contains system critical directories. I know that some phones make this memory accessible and then partition this memory in such a way to make the system directory inaccessible (which is on your internal SD card). But anyway, that was my first guess – and it was wrong.
My second guess should be right on the money.
You’re able to access the phone wirelessly, correct? That means your ADB/USB drivers are the culprit. I’m not sure what about CyanogenMod made this happen – it’s about 99% likely that it’s because CM9 on your phone is an ALPHA build. Alpha builds are so notoriously buggy that these kinds of problems are more the rule than the exception. However, supposedly USB connection works in CM9 for the Galaxy W. Something is clearly wrong.
Have you tried flashing CM7? That’s a thoroughly tested build and oftentimes superior in performance compared to newer versions of CM.
http://forum.xda-developers.com/showthread.php?t=1790721
Another possible issue is that your computer does not have the proper USB drivers installed. This is unlikely, however, as you previously had access before flashing CM9. To check for this, go to your device manager and check if the ADB/USB drivers installed. If they are anything like mine, you will see yellow – meaning they’re not properly installed. I have a lot of Android devices and not all of them are properly configured for USB connection.
Hope something in there works for you. Good luck!
The last thing i want to do is to remove all my memory again. Anyway, it has all the USB drivers (needed by ODIN to flash CWM)
August 2, 2012Ron, I’m sure you already checked such commonly used boxes as “Android
Debugging” (allow Android debug mode, ADB) in your settings menu. It
has led to complications in other devices (but this is probably not the
case in your situation). I’m still guessing it’s an ADB driver issue
witihin Windows.
I did some checking around and it appears that there are problems with
ADB drivers in Android 4. Try going to device manager and then
uninstalling and then reinstalling the required drivers – the user in
question is actually using a standard trouble-shooting method:
”I’m
pretty sure what worked was to plug the tablet into the computer with
the USB cable, go into device manager and find where the tablet is (I
don’t have it with me right now, so I can’t tell you where I found
it)… and then tell Device Manager to delete the device or forget it,
or whatever you do to remove the installed drivers…. From there plug
it back in and let it reinstall…”
He has some other suggestions:
“If
that doesn’t work, try a new USB port, I’ve found that it will try the
whole thing over again from a different port on the computer and might
be more successful with the next port.”
Personally, I like the first option more, but the second one should
August 3, 2012work too.
Argh. Sorry for the multiple posts – I just remembered one more thing. It could be that Windows is not properly recognizing the internal memory as an accessible drive.
Try going to “create and format hard drive partitions” from within Windows and scrolling through the list of your drives. If you see a drive equivalent in size to your phone’s internal storage, it’s likely that you need only assign a letter to the missing drive.
August 3, 2012Declan Lopez
October 1, 2012you may not have rooted it correctly