Related
Im having issues with the internal SD card after the update. So is Dennishwc
http://forum.xda-developers.com/showpost.php?p=10484065&postcount=1057
Via Windows 7 64 "Error 0x80070057:The parameter is incorrect 'for file copy and 'The file is too large for the destination file system' when I try to make a folders.
When I try to format in Windows, it shows capacity only as 2.19GB rather than 13gb or whatever it should be. Same occurs on a Win XP laptop I tried, but explanation of the errors are more general but seem to be the same.
Seems it might be this issue that 2.2 caused for the SGS Vibrant ?
http://forum.xda-developers.com/showthread.php?t=860328
http://forum.xda-developers.com/showthread.php?t=846384
Could just be the SD card failing unrelated to the update, but I have no idea. Seems I can copy to an external SD, and then copy via the phone to the internal SD. Odd.
I have tried format via Windows, which resulted in 2.19gb size, but phone reboot reset it to 13gb. Format via phone did not resolve either.
Any fix that will work? or is it borked.
I'll repost my question here.
Did you try the "format internal-sd" from CWM recovery ?
No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.
rye&ginger said:
No, Im new-ish to Android so I dont know all the apps to use yet, but have done phone hacking for years on Palm and iOS.
Seems CWM Recovery is a desktop app? I will try when Im off work.
Click to expand...
Click to collapse
Download Rom Manager from the market and run it. Click on install clockworkmod recovery. Then you can reboot into recovery. Please see the clockworkmod thread for more info
Sent from my SGH-I897 using XDA App
Don't forget to root first. I had a pain rooting this JL1. I spent 20 minutes playing with JL1 and I couldn't stand the lagginess. I'm sure lagfix would've helped, but I just went to a custom ROM instead.
Tried superoneclick only once and I'm rooted even went as far as unlocking it. Also, my phone isn't affected by the sd card bug. I can transfer files bigger than 2.19 Gb and it's showing the full size in Windows. Froyo runs flawless so far even though it's still not clear whether it's official or not.
Hmm, that's an odd one indeed.
Curious - I took a look at the 2 threads that Rye pointed out and one seems to be about external sd issues and the other about the mounting issues with 2.2 vibrant kernels. Doesn't seem like the problem you are having is either one of those... Could be but didn't seem that way upon review.
Did you happen to try and restore any backup after upgrading to 2.2 or anything? Can't imagine what would cause it but seems like it's getting mounted strangely or something... Surprised that a format internal sd wouldn't fix it in recovery...
Second question - what Samsung drivers / driver pack are you using on your Windows 7 x64 install? Wondering if the driver is failing to recognize the file system type and is causing Windows to treat it as a file system that shouldn't accept a file larger than 2+GB...
I havent noticed any problems with the size of the file. What happened with mine is that i transfered a couple of movies (about 3 or so) and then transfered about 4 gigs of music. halfway through the music it started giving me the error. after that, even transferring individual mp3 or pictures would result in an error. The internal sd card showed up on my computer as having 8gig free. after that i ran the check disk (by right clicking, going to properties then tools). my computer found errors and corrected them. after that, the internal sd card showed up as only having like less than a hundred mb left
Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19gb.
Im about to do the CWM recovery format and will post the results.
If you are using the Rogers 2.2 update with no kernel modifications then the CWM will not work for you.
The Froyo kernel from Samsung comes with Recovery 3e which RomManager can not replace for 2e as 3e requires digitally signed packages.
consider (i have not tried):
- root device
- adb shell
- su
- backup any files you need on /sdcard to /sdcard/external_sd
- use the format commands to re-format /sdcard
-- probably mkfs.vfat or the like.
rye&ginger said:
Riker2k, not sure if the drivers for Windows are the issue. I think I installed some drivers called SGH-i897_Captivate_USB_Drivers_5_02_0_2 that I got from the Samsung website, but I also just installed Kies to get the 2.2 update.
On the XP laptop, I was just using mass storage so it must have been generic drivers that were already on it.
To be clear, its usually shows as correct size in Windows explorer, but when I go to the format utility in Windows, it shows 2.19GB.
Im about to do the CWM recovery format and will post the results.
Click to expand...
Click to collapse
Yea, really not sure if the drivers are a problem or not. When I checked mine, running the Rogers 2.2, it shows the same as what yours does in the format utility - 2.19GB. That is odd because it seems to set the filesystem type as FAT32 which can easily handle the 13.0GB size of the volume. The properties in Windows show 13.0GB w/ about 11.0GB on my disk that is available...
Regardless, I would be hesitant to format or repair that disk within Windows. Who knows if there is something within Android that is put there as a translation layer that maybe Windows isn't seeing / reading correctly through the driver, etc. I'm sure someone does know but I'm not that guy so if anyone call fill in the details...
And, after just testing on my own system... bang, same issue trying to copy a 900MB file to it... Hmm, this just got interesting.
Going to check a couple of other things, will post result.
I had this exact same issue. The only fix for it that I could find was to do a complete restore of the stock rom. Oh well, nice to have a fresh phone.
Hmm, this is not a fun problem.
Just tested formatting the volume - from within the running phone only, mind you - and the result is strange. After copying everything from my SD card to my computer, with no issues, I unmounted the USB, formatted the card through the settings / sd card storage menu / format internal sd card. Took about 30 seconds after which point I reconnected the device, windows picked it up and I mounted it, recopied about 2GB worth of data to the card with no issues at all. Added an additional 500MB file to it with no issues. Disconnected the device from within windows using the safe removal tray tool, turned off usb connection on the device and then unplugged it. Remount the usb device and windows sees it no issues but I can't copy a single item or create a folder on it. Exact same errors as what Rye described and I encountered the first time.
So, seems like after a fresh format the sd card can be mounted in windows, ONCE, and then all hell breaks loose.
Why??? Will keep testing but looking like I need to move back to my previous di11igaf's ROM. Can't work like this...
Interested in what you find, Rye.
Oh btw, i am able to transfer files with no problems if i connect to the pc in media player mode. I have problems when i am in mass storage and kies connect modes
Riker2k, good stuff. I have no news, Im stuck where I am unless I swap the kernel it seems as I cant use CMW Recovery to format.
This is over my head, so I will for now probably just do a format, load up the card via Windows, and then use the external card to slowly add items when I want to and transfer over to the internal through the handheld. Ghetto. Either our Sd cards will get worse and die, or more people will have issues and it will get patched I guess?
Dennishwc, I will try media player mode but I think it did nothing when I connected that way the other day. I didnt mess with it much though. I need mass storage to use iSyncr app though, but there is a wi-fi add-on that may help me avoid that.
Well I just tried the format and dump a lot of stuff via Windows idea, and it only did about 2.2gb before the error stopped the fun. It did this twice, so this is is EXACTLY at the 2.19gb capacity that Windows is seeing in the format utility. So, I do have some news.
Again, this is over my head as to what to do next.
Has anyone tried moving files over via adb and see if you hit a 2.19GB limit?
I am having the same issue when copy files while connected in USB Mass Storage Mode (consistent).
On the plus side, I also tried connecting in USB Kies Mode, and I have yet to see this error. Copying is slower; but, it seems to work.
This could be a workaround for folks getting the error in Mass Storage Mode.
I am running Rogers 2.2 (all stock) and rooted with SuperOneClick.
i'm having the exact same problem. if i pick "mass storage" i can't copy anything over hte internal sd card, but if i use "media play" option, i can do it without any problem. i guess that's a temporary solution
i'm having the same problem, though the size and free space of the internal storage shows up correctly in my system.
i can also copy files no problem to the external SD when in mass storage mode.
Hello everybody. I'm facing internal SD storage malfunction. When the phone starts the memory is shown, only the system memory is at 0.00b, but after some time all memory becomes unavailable. After the phone starts and I quickly plug the usb I can access the internal SD storage and I can play files from it (the files were put before this happened). I think it is worth mentioning that before this I had error E:Can't mount /dev/block/mmcblk0p1 which restricted the phone form booting up. Then I flashed the stock rom (v2.2.1) and speedmod kernel and the phone booted. My phone model is i9000. I would be very grateful for any help you can provide. Thank you for advance.
PS. I have read a lot of articles about this memory problem but I couldn't find any specific solution for i9000.
wladylnik said:
E:Can't mount /dev/block/mmcblk0p1
Click to expand...
Click to collapse
try a solution for that problem from My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power
button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or
Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, &
KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Is it possible that I messed up my internal storage because I didn't turned off lagfix when I flashed new custom rom?
wladylnik said:
Is it possible that I messed up my internal storage because I didn't turned off lagfix when I flashed new custom rom?
Click to expand...
Click to collapse
yup, that is the main culprit for internal storage not being recognized as your partitions have may have been changed to ext4 and samsung original format is rfs
anewith aug
is it possible to fix this?
wladylnik said:
is it possible to fix this?
Click to expand...
Click to collapse
Its depends and not that easy but you can try solutions already mentioned in My Android Solutions
wladylnik said:
is it possible to fix this?
Click to expand...
Click to collapse
Just flash with pit file in odin.
Sent from my GT-I9000 using xda premium
I used your methods but nothing changed
wladylnik said:
I used your methods but nothing changed
Click to expand...
Click to collapse
read this
thanks for help xsenman but the problem still exists. I think the internal memory is dead. But it is strange that I can still view old stuff on it :|
Its not dead -_- you need to go into cwm recovery and format /sdcard. It'll delete all your files but might fix the problem.
Sent from the beast that ate my sisters iPhone 4S.
wladylnik said:
thanks for help xsenman but the problem still exists. I think the internal memory is dead. But it is strange that I can still view old stuff on it :|
Click to expand...
Click to collapse
you need to format all the partitions back to rfs (vfat or fat32) for samsung phones using firmware, lagfixing would have changed them to ext4.
I have checked the partition type with speedmod kernel and it shows that it is rfs not ext4. so the problem is something else.
wladylnik said:
I have checked the partition type with speedmod kernel and it shows that it is rfs not ext4. so the problem is something else.
Click to expand...
Click to collapse
If all internal partitions ( meaning system and data ) are rfs, firmwares will not have a problem. unless you had used onenand mode , where the sytem partion will be swapped with the data partition .
anyway the best way to resolve this, is to use the speed mode kernel and have your EXT SD card partitioned into two , to operate the phone like normal till you can resolve the internal sd card problem
after flashing i lost my internal and external storage
my firmware version is 2.3.3 ginger jpjv6
this is not my first time to use this rom it was working and after a while my internal and external storage unavailable
(sorry about my english im egyptian)
tal3t said:
after flashing i lost my internal and external storage
my firmware version is 2.3.3 ginger jpjv6
this is not my first time to use this rom it was working and after a while my internal and external storage unavailable
(sorry about my english im egyptian)
Click to expand...
Click to collapse
Why are you flashing -obviously - the same very old firmware again and again? There are so much better versions out there than old 2.3.3.
2.3.6 is a big improvement (android battery bug, power consumption, general stability).
Did you do a full wipe? If something is corrupt you have to do this. *2767*3855# resets everything.
i done it but still no internal and external storage
i done it but still no internal and external storage
tal3t said:
i done it but still no internal and external storage
Click to expand...
Click to collapse
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
---------- Post added at 05:59 PM ---------- Previous post was at 05:38 PM ----------
tal3t said:
i done it but still no internal and external storage
Click to expand...
Click to collapse
Did you have any lagFix applied on your Phone, when it was working?
[did you have any lagFix applied on your Phone, when it was working?[
no lagfix and my phone model is i9000
Could you please describe what exactly do you mean with "still no internal and external storage".
What does Task Manager > Memory show?
What does FileManager show? Are there no paths
/mnt/sdcard
/mnt/sdcard/external_sd
anymore?
Did you flash with odin while your external sd-card was still in the phone and it was destroyed this way? Please check the external sd-card with your PC and a card reader.
no internal storage
the only memory on the phone that works is the sd card and i installs the rom on it
Hayabusa_XDA said:
Could you please describe what exactly do you mean with "still no internal and external storage".
What does Task Manager > Memory show?
What does FileManager show? Are there no paths
/mnt/sdcard
/mnt/sdcard/external_sd
anymore?
Did you flash with odin while your external sd-card was still in the phone and it was destroyed this way? Please check the external sd-card with your PC and a card reader.
Click to expand...
Click to collapse
the external sd card is working but usb storage is unavailable and here a an image to what i mean
tal3t said:
the external sd card is working but usb storage is unavailable and here a an image to what i mean
Click to expand...
Click to collapse
seems both sd-cards are not mounted anymore.
If you had reset everything anyhow so there is no configuration worth to be saved I would reflash everything anew (guess you're using odin)
PDA
MODEM/(PHONE)
CSC
!including! "Re-Partition", i.e. with PIT file. Be careful to choose the right one, should be a 512 pit in your case.
Hayabusa_XDA said:
seems both sd-cards are not mounted anymore.
If you had reset everything anyhow so there is no configuration worth to be saved I would reflash everything anew (guess you're using odin)
PDA
MODEM/(PHONE)
CSC
!including! "Re-Partition", i.e. with PIT file. Be careful to choose the right one, should be a 512 pit in your case.
Click to expand...
Click to collapse
reflashed but same problem
tal3t said:
reflashed but same problem
Click to expand...
Click to collapse
Sorry, no more ideas.
SGS's flashable rom (8GB) is one big piece of ROM, logically divided by software into several partitions like a PC's harddisk. It is very unlikely that every part is working but only the part with the "sd-card" is corrupt.
Similar to PC there is a bootloader, a partition table and the partitions itselves, each formated with a certain file system (Samsung's rfs by default).
If you're doing an Odin flash with re-partitioning almost everthing with the exception of the bootloader should be rewrittten anew, e.g. partition table and in the ongoing process you could notice Odin messages formatting the partitions anew.
Is there any hint in this Odin log that some partitions could not be formatted anew?
Did you change the filesystem before to some exotic / unknown system?
Are the files you're flashing really working / good ones?
Did you flash the right file into the right "Odin"-folder? (PDA to PDA, MODEM to Phone, ...)?
If you're flashing a working firmware with reformat the partition table should be OK and of course these new and clean partitions should be mounted automatically when booting the phone.
In reality there there is more, e.g. your phones IMEI is stored in one hidden partition. So although this is no solution but it would be interesting to know if your phone still has its IMEI number or MAC-address?
It happened after formatting it with NTFS (it was a temporary thing so I can use it with one of Microsoft services), and my device is working and rebooting properly without any error messages..So what can I do now to make my SD working again?
(I don't really need the data that was on it, I just need the card to work)
Thanks..
ramy670 said:
It happened after formatting it with "Windows7-USB-DVD-Download-Tool" (I was trying to use it as USB flash memory in order to install windows), and my device is working and rebooting properly without any error messages..So what can I do now to make my SD working again?
(I don't really need the data that was on it, I just need the card to work)
Thanks..
Click to expand...
Click to collapse
try formatting the card from within CWM, i presume if you boot up the phone you can't mount/unmount it and subsequently format it from within Android.
but i would try fromating it as FAT32 from within Windows 7 first, NTFS is not supported by Android to the best of my Knowladge...
Thanks, yes I can't format it in Android since i can't mount it, I've already tried formatting it from CWM with no luck, it showed this:
Formatting /sdcard...
Error mounting /sdcard!
Skipping format...
Done.
And windows doesn't see the card at all when I connect phone to PC, so I can't use windows to format it too.
ramy670 said:
so I can't use windows to format it too.
Click to expand...
Click to collapse
Try a formatting tool or recovery tool in My Android Collections
olaf2k4
Turned out you're right, the problem is android not being able to handle NTFS properly, I tried to format external SD card with NTFS to see what will happen, and I had the EXACT same symptoms, but of course I removed from phone and had it formatted using card reader and it's working properly now with my phone..
xsenman
The problem now is that windows can't see internal card at all, I've tried one of format tools form the link you put, but it didn't help since phone "doesn't allow" windows to detect the memory, any other way to do it? right now I'm trying this:
http://forum.xda-developers.com/showthread.php?t=1724078
It seems like it isn't easy to install NTFS support from the link above (since you need fuse.ko file that should be compiled for both your device and ROM), is there any kernal that support NTFS or any other easy way to do it?
If you are talking about your external sd just format at fat32. This is standard for sdcards and your phone wil reconize your card..
Unfortunately it is the internal one..
ramy670 said:
Unfortunately it is the internal one..
Click to expand...
Click to collapse
ny solutions?? :crying:
me facing same problems... phone doesn't detects internal sd, neither it connects to pc via mass storage... :crying:
I don't care about the data in it even if its gone, I jus want my internal sd back...
Anyone?..
Swaps100050 said:
ny solutions?? :crying:
me facing same problems... phone doesn't detects internal sd, neither it connects to pc via mass storage... :crying:
I don't care about the data in it even if its gone, I jus want my internal sd back...
Click to expand...
Click to collapse
Finally, I found a solution, just do the following (I tried it and it worked):
1. First install the drivers ONLY if you haven`t already installed them, also if you have Kies installed there is no need to install these drivers, but you are better off installing these anyway : http://dev-host.org/ZRA
2. Download this package (it includes i9000 stock rom+kernel+odin) : http://dev-host.org/RAE, if you have a Captivate or a Vibrant just download a stock rom for your phone model and find a kernel which has root and cwm in it.
NOTE : The next step will require using the 3 key combo for accessing the clockworkmod recovery and also the download mode.The 3 key combo used below is for the Samsung Galaxy S GT-i9000. If you own a Captivate or a Vibrant please click this link and choose your phone model to see what 3 key combo must be used, as it differs from one phone model to another : http://tinyurl.com/6q6ajpx
3. After you have extracted all the contents you downloaded and installed drivers, put your phone into download mode using the 3 key combo : volume DOWN + home button+power button, keep those pressed until it goes into download mode.
4. Connect phone to PC via USB Cable and open Odin (windows should detect the phone and install some drivers, after it`s finished you should see the message "Added!" in Odin which means Odin succesfully detected your phone so now you are ready to flash)>check Re-Partition Option>press PIT button and browse for the s1_odin_20100512.pit file, press BOOTLOADER button and browse for the APBOOT… file, press PDA button and browse for the CODE….file, press PHONE button and browse for the MODEM….file, press CSC button and browse for the GT-I9000-CSC….file. PRESS START button and wait for the green pass notification in Odin.
• When the phone reboots into the rom, wait for the setup wizard to appear and then just use the 3 key combo into the download mode again.
Close Odin and open it again> press PDA button and browse for CF-Root…file> Press START button and wait for the green pass notification in Odin.
Click to expand...
Click to collapse
ramy670 said:
Finally, I found a solution, just do the following (I tried it and it worked):
Click to expand...
Click to collapse
No need to do all this.
Just:
- remove external sd card (if you have one inserted)
- reboot into CWM-based recovery
- mounts and storage
- mount USB storage
You will be able to see and format, FAT32, the disk using windows
N3tMast3r said:
No need to do all this.
Just:
- remove external sd card (if you have one inserted)
- reboot into CWM-based recovery
- mounts and storage
- mount USB storage
You will be able to see and format, FAT32, the disk using windows
Click to expand...
Click to collapse
hello, i also did this stupid mistake on my part. Formatted the Internal memory of my Pantech Burst to NTFS. Now its unformattable, unmountable etc. I tried ur way, but it throws up an error
"Unable to write to ums lunfile (no such file or directory)"
wat to do ?
Swaps100050 said:
ny solutions?? :crying:
me facing same problems... phone doesn't detects internal sd, neither it connects to pc via mass storage... :crying:
I don't care about the data in it even if its gone, I jus want my internal sd back...
Click to expand...
Click to collapse
what i did was to go in recovery mode...mount usb ...conect to pc and reformat to fat 32..
harryneopotter said:
hello, i also did this stupid mistake on my part. Formatted the Internal memory of my Pantech Burst to NTFS. Now its unformattable, unmountable etc. I tried ur way, but it throws up an error
"Unable to write to ums lunfile (no such file or directory)"
wat to do ?
Click to expand...
Click to collapse
Are u able to wipe data/factory reset? If u are able to do so do it and then follow my procedure... if u are not able, try to follow my procedure more carefully. It is the only thing I can suggest, sorry
N3tMast3r said:
Are u able to wipe data/factory reset? If u are able to do so do it and then follow my procedure... if u are not able, try to follow my procedure more carefully. It is the only thing I can suggest, sorry
Click to expand...
Click to collapse
I tried your method, but selecting "Mount USB" was throwing the error i mentioned in my last post. Though i solved it eventually. Somehow i ended up in the phone's own recovery/bootloader menu, had an option of "Low level format" there. Took around an hour or so .. but it worked :good:
I've had a Chromecast with Google TV for about a week. I added a usb stick for added memory . I'm in developer mode and have unknown sources on. Using the X-plore file manager, I sideloaded games with obb files onto the drive with no problem. However, a few days later, the Chromecast got laggy (unrelated I hope) and I had to do a factory reset. Since then, X-plore will not show the USB drive if I'm using the USB stick as device storage. I'm pretty sure that was the way I had the stick formatted before. When the stick is formatted for external storage, I can't transfer data to it. When it's formatted as device storage, it's not recognized on the file manager. Also, the file manager won't allow for an obb folder. I get a msg saying it's not allowed.
How did I screw this up? Please help :fingers-crossed:
Thanks from a confused noob
is it fat32?
drchip42 said:
is it fat32?
Click to expand...
Click to collapse
Yup.
I think I figured it out last night. After I factory rebooted it, I didn't change some of the storage permissions on the apps .
Can't seem to get passed read only error with x-plore. Do I need to format to fat32 and how. PC is old and only gives me option for exfat and ntsf. Thanks in advance