As a newcomer to the world of android (I just migrated from iPhone 4), I must confess that the multitude of advice and recommendations from the advise givers are clouded with wrong advice and misleading recommendations.
I am very knowledgeable in computers, and was quite knowledgeable with the various iPhones I owned. but with the Galaxy S (Captivate) I just purchased I am ready to give up....
Is there anybody kind enough who can explain to me why is it that I am unable to access my phone from my computer (W7x64 nor from my MacBook).
I was able to root the phone and even flash it with the Froyo, Cognition 2.2 Beta 5.5, from the phone itself (using the online advice from the Cognition web site), but can not access the phone, thus unable to move files to the SDCARD root directory.
download the kies mini application from samsung.com
install it, which will install the drivers needed.
then go to settings->application->usb and select usb storage.
then go to touchwiz home screen only, and plug in your phone.
easy peasy...
if you have another launcher in place, turn on usb debugging under the development section of applications in settings and then plug it in... then pull down notification from top and select usb.. it will ask you to mount.
boom... done and done.
Semi wrong info is given above. For a mac(I also have a pro) you should just have to turn on usb debygging mode under application settings. You will not be able to control the phone as easily as with the iphone but you will have access to your sd card and internal memory.
No need for drives but you will need to mount it
Sent from my SAMSUNG-SGH-I897 using XDA App
And on a pc, enable usb debugging in settings-applications-development. Then pull down the notification screen and press the option that says something like select to copy files. You can then access the internal and external sd cards as drives on your computer.
Sent from my SAMSUNG-SGH-I897 using XDA App
mobius911 said:
And on a pc, enable usb debugging in settings-applications-development. Then pull down the notification screen and press the option that says something like select to copy files. You can then access the internal and external sd cards as drives on your computer.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Actually, you don't need to enable USB debugging, you just select the option to "always ask" or "mass storage" and then you get the pull down option to mount the drive to copy files.
alphadog00 said:
Actually, you don't need to enable USB debugging, you just select the option to "always ask" or "mass storage" and then you get the pull down option to mount the drive to copy files.
Click to expand...
Click to collapse
Interestingly that option stopped working for me many ROMs ago. Not sure why, bu the only way I could do it was using the debugging route. I am currently on Cognition 2.2Beta5.5, so I decided to check mass storage since I hadn't tried it in a while. It worked! So if anyway else out there can't do it using "always ask" or "mass storage", then the debugging method can be used as an alternate. Thanks for bringing this up.
And as a general comment on the original title of the post, things move fast. What was accurate for one person on his/her phone at one particular moment may not be the best or even the right way to do it on your phone, in your situation, with whatever ROM you are running. So if you want to hack your phone then expect to have to spend a lot of time reading and perhaps even making a few mistakes along the way.
Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?
Brian44 said:
Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?
Click to expand...
Click to collapse
Try to take out your SD card and put it in a Card reader, remember to do it while your device is off or unmount it from memory settings, try to swtich on your device later and connect it to your computer and check if it connect through USB or not.
Try some system tools?
Brian44 said:
Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?
Click to expand...
Click to collapse
I'm guessing databaiz's suggestion to take out the card isn't an option because it's the internal sd card, right? If so, for the one-in-a-million chance that the external card is screwing with the bus, I'd take the external card out and reboot anyway, just to make sure; if it works OK then, I would check the external card as databaiz suggests. But assuming it still doesn't work, next question is, do you have a terminal app installed? Please try the 'mount' command and let us know what you see. One other question, will it still go into fastboot mode? Can you see it from your computer when in fastboot mode (the details of how to do this depend on whether you have windows or linux/macOS - I can maybe help with the latter, but not the former).
It could be bad card
It could be bad card.... Remove and test in card reader...
cannot access internal or external storage
Thanks guys, I have been booting without external memory, with problems still the same. So, cannot be problem with external SD.
The internal SD card is not accessed properly. When I go to settings>Apps>All, the line at bottom shows Internal storage 4.1 MB used, 798MB free. (I have uninstalled most apps to see if that helped – it did not.) So, something is accessing the internal SD, also apps are running which must be off the internal SD.
I do not know what a terminal app is, Urilabob. I have downloaded it but what do I do with it?
At: [email protected]:/ $ I keyed in # mount [enter] , making:
[email protected]:/ $ # mount [enter]
But nothing happened, just another line of: [email protected]:/ $
Also, what is fast boot mode – this is not the same as sleep mode? This is all new to me. Appreciate your help.
My laptop is Windows 7.
Brian44 said:
Thanks guys, I have been booting without external memory, with problems still the same. So, cannot be problem with external SD.
The internal SD card is not accessed properly. When I go to settings>Apps>All, the line at bottom shows Internal storage 4.1 MB used, 798MB free. (I have uninstalled most apps to see if that helped – it did not.) So, something is accessing the internal SD, also apps are running which must be off the internal SD.
I do not know what a terminal app is, Urilabob. I have downloaded it but what do I do with it?
At: [email protected]:/ $ I keyed in # mount [enter] , making:
[email protected]:/ $ # mount [enter]
But nothing happened, just another line of: [email protected]:/ $
Also, what is fast boot mode – this is not the same as sleep mode? This is all new to me. Appreciate your help.
My laptop is Windows 7.
Click to expand...
Click to collapse
Sorry, I replied earlier but it seems I messed up so the reply didn't appear.
My problem is I know unix fairly well, and android is very similar, so I forget what is the same and what's different. Sorry, the command you need in the terminal is "df". That will show you a list of what partitions are mounted on your system. I'm guessing you're going to see /system, but not /mnt/sdcard. Why, I don't know. It's possible that the sdcard partition has got corrupted - but suspicious that the external card is also having problems. Is it possible that either the tablet or your pc crashed while you were copying files between them? Or that you disconnected the cable between them before telling the tablet to go out of connected mode? Either of those could explain corrupted partitions. Unfortunately fixing them may not be easy.
There are three different ways to connect your tablet to a computer. One is so it looks like external disks. I got the impression you already discovered this, and that it has now stopped working. The other two require you to install (parts of) the android development system on your computer. The simplest one is adb mode. Please google it to see how to use it. This might give you a chance to check the state of your partitions. The other is in fastboot mode. Fastboot mode is an alternative way of starting your computer, that goes into a fairly bulletproof, but very simple, mode that allows you to do various things on your tablet (it gives you very low level access to the tablet - powerful but dangerous). I'm pretty sure it will still be working. How you get into fastboot mode depends on your tablet; you'll need to google it. And how you access it in fastboot mode is fairly different on windows. So I'm not the best adviser. But please be careful - it's easy to brick the tablet in fastboot mode, you need to make sure you completely understand any steps you might take, especially any that might write to the tablet (of course, reading from it is safe). And of course the simplest alternative is simply to completely reinstall the tablet (sorry, I forget the android term for this). That should restore things OK, but it will mean you lose all your data and will have to reinstall all your applications.
cannot access internal or external storage
urilabob said:
Sorry, I replied earlier but it seems I messed up so the reply didn't appear.
My problem is I know unix fairly well, and android is very similar, so I forget what is the same and what's different. Sorry, the command you need in the terminal is "df". That will show you a list of what partitions are mounted on your system. I'm guessing you're going to see /system, but not /mnt/sdcard. Why, I don't know. It's possible that the sdcard partition has got corrupted - but suspicious that the external card is also having problems. Is it possible that either the tablet or your pc crashed while you were copying files between them? Or that you disconnected the cable between them before telling the tablet to go out of connected mode? Either of those could explain corrupted partitions. Unfortunately fixing them may not be easy.
There are three different ways to connect your tablet to a computer. One is so it looks like external disks. I got the impression you already discovered this, and that it has now stopped working. The other two require you to install (parts of) the android development system on your computer. The simplest one is adb mode. Please google it to see how to use it. This might give you a chance to check the state of your partitions. The other is in fastboot mode. Fastboot mode is an alternative way of starting your computer, that goes into a fairly bulletproof, but very simple, mode that allows you to do various things on your tablet (it gives you very low level access to the tablet - powerful but dangerous). I'm pretty sure it will still be working. How you get into fastboot mode depends on your tablet; you'll need to google it. And how you access it in fastboot mode is fairly different on windows. So I'm not the best adviser. But please be careful - it's easy to brick the tablet in fastboot mode, you need to make sure you completely understand any steps you might take, especially any that might write to the tablet (of course, reading from it is safe). And of course the simplest alternative is simply to completely reinstall the tablet (sorry, I forget the android term for this). That should restore things OK, but it will mean you lose all your data and will have to reinstall all your applications.
Click to expand...
Click to collapse
Thanks, Urilabob. The command df had an effect!
Shows Filesystem with figures for Size, Used, Free, and Blksize (4096), next to each of the following:
/dev, /mnt/asec, /mnt/obb, /system, /data, and /cache. The figures are all different except Blksize.
/mnt/sdcard is not shown.
Does this tell you anything useful?
I have never been able to access the tablet from my laptop with Windows 7. My son’s laptop has an earlier Windows, so I checked today and found that his Windows Explorer finds the tablet (as 2 disks, A and F) and asks “Please insert a disk into Removable Disk H:” (and same for F.
By the way, this problem started when I downloaded the (automatic) firmware update direct to the tablet, not via laptop. But the wifi signal was weak, and files may have been corrupted. I have since downloaded the complete, latest firmware to the laptop (with strong wifi signal), but do not know how to get it into the tablet!
Have not yet done anything on adb or fastboot modes. Will Google adb tonight.
Not worried about losing data or apps.
Thanks again, Brian.
I'm guessing that your tablet is rooted? If so, do you have an app like superuser? I remember having to go through some options to give my file explorers access to my SD card. You may have accidentally set you SD card to be off-limits or something. If you haven't already done it, see if giving an app like ES File Explorer superuser access will help.
Also see if you can enable USB debugging. For my nook color, I have to enable in order to access usb mass storage for one of my memory units. See if you can access your internal SD card content through USB debugging.
cannot access internal or external storage
SacTappingUni said:
I'm guessing that your tablet is rooted? If so, do you have an app like superuser? I remember having to go through some options to give my file explorers access to my SD card. You may have accidentally set you SD card to be off-limits or something. If you haven't already done it, see if giving an app like ES File Explorer superuser access will help.
Also see if you can enable USB debugging. For my nook color, I have to enable in order to access usb mass storage for one of my memory units. See if you can access your internal SD card content through USB debugging.
Click to expand...
Click to collapse
Thanks for your thoughts. My tablet is not rooted. And I cannot enable USB debugging, because Settings freezes when I tap Developer Options to get to USB debug. I am just learning about Android - seems to be 2 partitions on the internal storage, one about 2.6GB with apps and other things on (which is accessible), and the other partition must be about 13GB, but has not been accessible since the automatic firmware update.
Sounds like the update caused you issues. If you have everything backed up with your Google account I recommend that you do a factory data reset and see if that fixes your issue.
cannot access internal or external storage
MissionImprobable said:
Sounds like the update caused you issues. If you have everything backed up with your Google account I recommend that you do a factory data reset and see if that fixes your issue.
Click to expand...
Click to collapse
Factory reset would be great, if it worked, but it does not function.
Can you exchange the device?
Brian44 said:
Factory reset would be great, if it worked, but it does not function.
Click to expand...
Click to collapse
OK, so from your df listing, it's clear that sdcard is not getting mounted. That's a pretty low-level function that is failing. The fact that factory reset also doesn't work suggests (doesn't prove) that the sdcard partition at least has a corrupted filesystem, and quite possibly the partition itself has been corrupted. Could a spotty OTA update do that? I'm surprised - I would have thought they would use fairly high level functions for OTA updates, precisely because any drop-out could cause corruption if you use low-level disk access. But who knows - the mysteries of google? Another possibility is that the sdcard is physically bad, and maybe the update just caused you to get into the bad region (with the dynamic memory mapping in flash memory, once something goes wrong it's almost impossible to figure out what). At this point, I'd be going back to the distributor if possible (you said it was new, right)? I think even if you were an android guru, and knew exactly how to do a complete rebuild from scratch, you would be risking that the device itself is faulty - and that the rebuild would mean you couldn't prove that the device was at fault (rather than your rebuild)...
Best Wishes
Bob
cannot access internal or external storage
urilabob said:
OK, so from your df listing, it's clear that sdcard is not getting mounted. That's a pretty low-level function that is failing. The fact that factory reset also doesn't work suggests (doesn't prove) that the sdcard partition at least has a corrupted filesystem, and quite possibly the partition itself has been corrupted. Could a spotty OTA update do that? I'm surprised - I would have thought they would use fairly high level functions for OTA updates, precisely because any drop-out could cause corruption if you use low-level disk access. But who knows - the mysteries of google? Another possibility is that the sdcard is physically bad, and maybe the update just caused you to get into the bad region (with the dynamic memory mapping in flash memory, once something goes wrong it's almost impossible to figure out what). At this point, I'd be going back to the distributor if possible (you said it was new, right)? I think even if you were an android guru, and knew exactly how to do a complete rebuild from scratch, you would be risking that the device itself is faulty - and that the rebuild would mean you couldn't prove that the device was at fault (rather than your rebuild)...
Best Wishes
Bob
Click to expand...
Click to collapse
Thanks, Bob for all your help. This seems like the end of the line with this tablet. I expected this might be the case, and emailed DinoDirect two days ago for a refund, as I am heading overseas next week and want to resolve the matter before I go. They responded that "we will contact our related department to process your case priority". I have been aware that any actions I might take could invalidate the warranty, and this has inhibited me a bit. I will forward your latest comments in support of my refund claim.
I learned some basics of Android from all this!
Good wishes, great talking to you.
Brian
Just for a great justice :victory:
Got same bug on my Gemei G6, guess it hapens after i connect dc cabel to a fully charged pad that was charged in off mode and turn on. So i just download last firmware fro Gemeitech.com, unzip it on SD card and tnen turn on pad with pressed Home and Power buttons that must be pressed untill robot with green rotating belly appears what mean start of flashin` Thats it.
Got the same issue in Huawei Ascend P-7, I just switched off the mobile, removed the SD card and turned it back on after 5 minutes ....... and that was it, all issues resolved. Just the thing was that once SD card was re-inserted, problem came up again. So i have decided to copy SD card data to PC via Card Reader and format it or get new SD card
I have moved an SDCard to a new phone with Android 4.4.
Since that time I cannot see the camera files when connected mass storage in a windows 7 machine. The files that are visible on the computer are from last year, before the move of the card to a new phone. They are all on the SDCard, removable. I removed the SDCard from the phone and all the old files are there.
The camera app is apparently saving new pictures to internal storage. Which does not mount USB.
I should say, a while ago my internal storage got full and I went through and selected "Move to SDCard" on most apps. I don't think that is related, but I am no expert.
I have two camera items in gallery. I can see all the files, new and old, and can send any of them with an SMS message. No problems. When I removed the SDCard gallery only had one camera item.
So to troubleshoot, I have downloaded ESFileExplorer. That can see all the files.
But when I connect to USB and enable USB storage, I can only see the removable card. To test I removed the SDCard from the phone and installed it in a card reader, I can see all the files now.
I do notice one difference now, when I connect the phone to USB with no SDCard installed I get the usual message to enable USB storage, and I click the button, it chuggs, and goes back eventually to the same message, and the USB storage is indeed not mounted. So the stock phone with no SDCard will not mount USB storage, though it offers to.
I have two notifications in the notification pane, one "USB connected" with the robot and the button "turn on usb storage".
I also have a different notification "connected as mass storage" which when selected has four entries, SDCard, which is selected, and PTP, MTP and Charging.
But it seems even though SDCard in checked, it's not actually mounted for some reason.
Any ideas, or is the idea of putting an SDCard in an android phone now a bad idea because of this?
My reading indicates this might be a problem introduced with the permissions changes with KitKat. If so, they really need to fix that. But judging on all the fighting on security issues on Bugzilla which results is just plain wrong development decisions, well, I get it. But I just had to ask you guys who probably actually know.
Firstly, try to be more concise when have problems, post the things you have tried in numbers or columns so somebody who might want to help can quickly know what you have tried and suggest something.
I did not read past your 2nd paragraph.
Secondly, I had a problem with my own sdcard, a kingston 16gb, in the past. Long story short, it became unreadable in my phone. Try to connect it to a PC, if you have an adapter, and back your files there.
The only solution for me was formatting it in my PC. After the format, it works for now.
I also switched phones, formerly a phone running CM11, now a phone running stock Sony 4.4 firmware.
Lastly, it might have to do with the fact that, whatever phone you switched to, some folder naming causes issue for the OS to read.
Again, back your files up, format the SD card.
shadowcore said:
Firstly, try to be more concise when have problems, post the things you have tried in numbers or columns so somebody who might want to help can quickly know what you have tried and suggest something.
I did not read past your 2nd paragraph..
Click to expand...
Click to collapse
Hmm.. Well, then thanks for the response.
shadowcore said:
Secondly, I had a problem with my own sdcard, a kingston 16gb, in the past. Long story short, it became unreadable in my phone. Try to connect it to a PC, if you have an adapter, and back your files there.
The only solution for me was formatting it in my PC. After the format, it works for now.
I also switched phones, formerly a phone running CM11, now a phone running stock Sony 4.4 firmware.
.
Click to expand...
Click to collapse
As I said, the card is readable on a pc, and on the phone. It's hard for me to think that is the answer. I did all that, and posted it.
shadowcore said:
Lastly, it might have to do with the fact that, whatever phone you switched to, some folder naming causes issue for the OS to read.
Again, back your files up, format the SD card.
Click to expand...
Click to collapse
Now that's an idea.
Before I try that I will see if anyone else has any ideas.
But that doesn't explain why the USB storage does not mount when I connect USB with the SDCard removed from the phone. It tries but never mounts. I think that is a clue.
I was gonna post a link to esr's "how to ask questions the smart way", but I don't have enough rep to post the outside link to catb.org.
I do try to follow that approach, and though I am new here I am NOT new to forums. I have been doing this, well, longer by far than most. A lot.
Well, still no change. I may just get another SDCard, put that in and see if that one exhibits the problem.
Virtual?
I did get another SDCARD, no difference.
I need to find the issue here.
I noticed I have two camera items in gallary, one has a camera icon and one has a folder icon.
The one with the camera icon only contains old pictures, from before migration.
The one with a file folder icon contains current pictures, taken by this phone.
When I plug into a computer as USB storage, only the old one mounts, the one with the camera icon. The new pictures (folder icon in gallery) do not mount.
Clearly this seems like a virtual filesystem that has it's pointers slightly wrong.
The camera app is saving it's photos in a directory that is not mounted when USB storage is used. It's not in the SDCARD, but it is in the internal memory.
The camera subdir that is a folder icon should be the one mounting as USB storage, and the other folder should be virtualized as a part of that.
I guess the problem is Kitkat does not save camera pictures on the SDCARD if available, as previous android versions did.
Can anyone suggest steps to isolate this problem?
hi I have a problem where I cant get in my eyes the best fetcher in MM update. I cant seem to make my memory card work as internal storage I have a tablet with the same memory card and that feacher works just fine. is this a setting in a odd place or did Samsung take it out
It's not enabled on samsung devices but there is a way to do it. I do think have a link to where but people say it's the same was you enable it on an s7.
Sent from my SM-G900P using XDA-Developers mobile app
zune70 said:
It's not enabled on samsung devices but there is a way to do it. I do think have a link to where but people say it's the same was you enable it on an s7.
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
that's sad that Samsung would do that. I hope there is a dev that is willing to fix this. I am more then willing to test.
I found a fix its tested and working on my sprint S5 with the new update 6.0.1
only one thing I noticed some times the apps don't go to memory card so they have to be manually put there the old way by going to the app and telling it to go to the SD card
follow the steps in this link
http://www.modaco.com/news/android/...e-adoptable-storage-on-your-s7-s7-edge-r1632/
also here is the walk though from the link its stats its for the s7 but I have the S5 and it works for that as well so Enjoy
f you've been following the launch of the Samsung Galaxy S7 / S7 Edge, you may have read that adoptable storage, a Marshmallow feature that lets you use the microSD card just like internal storage, is missing. The S7s do include a feature where you can move apps to SD card, but it's not quite the same. The good news? You can enable the feature using ADB and it seems to work great, including in hybrid ('mixed') mode.
In order to set adoptable storage up, you will need a computer with working 'adb' and, of course, a microSD card in your phone, the faster the better (I personally use a 128GB EVO+ in my own device. Here's the process!
1. BACK UP THE DATA YOU HAVE ON YOUR MICROSD CARD. Your card will be formatted by this process, so make sure you have saved any pictures, videos etc. from your card to your PC before you start.
2. Decide how you want to split your card. You can either commit 100% of the card to internal storage, or split between internal storage and conventional SD. This option is useful if you like to unplug your card and put it in your PC. I would probably recommend committing the whole card.
3. Open your command window / terminal on your computer and type the 'adb shell' command (with your phone connected of course). You will need to enable USB debugging in developer settings (which in turn is displayed by tapping the build number of the device 5 times) in order to see the option.
4. Type 'sm list-disks' to list the disks available for adoption. It'll look something like below - take note of the disk ID (disk:179:160 in this example).
5. Partition the disk. For this we use the 'sm partition DISK TYPE RATIO' command. For example, to partition the disk above as fully adopted storage (aka private) I'd use the command 'sm partition disk:179:160 private'. If I wanted a 50/50 split between adopted and regular, I'd use the command 'sm partition disk:179:160 mixed 50'. Easy right?
6. This process will take a while, but when it's done, the Settings -> Additional Settings -> Storage view on your device should show the new Internal Storage. Note that, for some reason, the total space isn't reported correctly as you can see in this image, however everything seems to work OK. When you install apps, they will generally install automatically to the storage with the most space available, although you can manually move things around if you want to, perhaps for performance reasons (the real Internal storage will likely always be a bit faster).
7. If you want to see another view of how you are doing for space, you can use a third party tool such as FreeSpace or FreeSpace Plus.