Related
Recently I had this issue with my Galaxy S I9000B, the system seems to have saved a permanent image of itself, and recovery it on every bootload, once that everytime i reboot it all changes i had made vanish, i mean it keeps old apps old settings...
It looks like the system took a "printscreen" of itself on a specific moment and now everytime the phone is rebooted this "printscreen" is restored.
During my epic jorney trying to solve the problem, i'd killed the stock rom (eclair) and installed a CWM kernel, and tried some adjusts at CWM Recovery Mode, and that's what I've noticed:
Under Mounts and Storage Menu, I can't mount or format: /data and /emmc
If I mount USB storage with /sdcard mounted and move a file into the Internal sd card (through Windows Explorer), the file remains at the sd card after i umount and remount the USB Storage, but vanish after the reboot, or if I umount /sdcard.
If I mount USB storage without /sdcard mounted and move a file into the Internal sd card (through Windows Explorer), the file vanish at the sd card after i umount and remount the USB Storage.
OBS[1]: the same thing happens if I try formating the SDcard (even low level formating) under the previous circumstances.
It seems I've burned every neuron on this task =P, and belive me i'd google it...a lot!!!So can anybody help me?
Nobody???
I've reinstalled the stock eclair ROM, it seems the part of memory that keeps the operation system is not affected by problem whatever it is and now I'm able to make the root at least until I reboot
recovery.log file, if it helps...
I dont know much about what your problem is,but you should check 2 things :
1 - A program that does that backup & restore . Maybe you have one in your phone and it messes up things .
2 - Backup your rom (in recovery,in case the next operation wont do any good) and then wipe everything . Data,cache,dalvik cache,everything .
I had a similar problem with " not saving" for my internet access point name . I created a new one and it would reset in about half an hour to default and delete the apn i created . Wiping solved my problem ,good luck .
rekatluos said:
I dont know much about what your problem is,but you should check 2 things :
1 - A program that does that backup & restore . Maybe you have one in your phone and it messes up things .
2 - Backup your rom (in recovery,in case the next operation wont do any good) and then wipe everything . Data,cache,dalvik cache,everything .
I had a similar problem with " not saving" for my internet access point name . I created a new one and it would reset in about half an hour to default and delete the apn i created . Wiping solved my problem ,good luck .
Click to expand...
Click to collapse
Thanks for the answer...but I don't have any backup programs and i've never performed a backup on this phone...about the wipe...it produces no effects....
Hi,
I already asked for this issue in the this Thread, but didn't got any answer.
I tested these three JB ROMS: CM10, HellyBean and SlimBean.
All of them work nice, except that my internal sdcard does not mount at boot time.
I have to do it manually every time boot up my phone by choosing System Settings --> Storage --> Mount SD card
Anyone have the same issue?
Does anyone have a solution?
Thanks
Same here! Google found this post, perhaps it will find us an answer
xalo2k said:
Hi,
I already asked for this issue in the this Thread, but didn't got any answer.
I tested these three JB ROMS: CM10, HellyBean and SlimBean.
All of them work nice, except that my internal sdcard does not mount at boot time.
I have to do it manually every time boot up my phone by choosing System Settings --> Storage --> Mount SD card
Anyone have the same issue?
Does anyone have a solution?
Thanks
Click to expand...
Click to collapse
toddmworth said:
Same here! Google found this post, perhaps it will find us an answer
Click to expand...
Click to collapse
I have the same issue with my I9000.
Any JB with different kernels makes the internal SD eventually be unmounted. When install a JB ROM the phone works very well but suddenly, the internal SD (phone's SD) is unmounted.
In CWM both SD are mounted and read without any problem. With ICS ROMs the phone works flawlessly.
In my case, the external SD is functioning as expected.(I have a 32 GB micro sd)
The installation language is Spahish - Spain.
No matter which method of cleaning and wiping I use, the result is the same.
Also, starting from GB stock firmware (JVU) flashed with Odin, followed by installing the nightly Cianogen CM10.1 and finally flashing the desired JB ROM works.
I tested Helly Bean, Slim Bean, C-ROM Mix and Baked Blacjbean7 obtaining the same behaviour.
Important: I'm restoring around 54 apk using Titanium backup (games, applications and utilities) in every case. I did not tested the ROMs without these restorations.
marcelogabriel said:
I have the same issue with my I9000.
Any JB with different kernels makes the internal SD eventually be unmounted. When install a JB ROM the phone works very well but suddenly, the internal SD (phone's SD) is unmounted.
In CWM both SD are mounted and read without any problem. With ICS ROMs the phone works flawlessly.
In my case, the external SD is functioning as expected.(I have a 32 GB micro sd)
The installation language is Spahish - Spain.
No matter which method of cleaning and wiping I use, the result is the same.
Also, starting from GB stock firmware (JVU) flashed with Odin, followed by installing the nightly Cianogen CM10.1 and finally flashing the desired JB ROM works.
I tested Helly Bean, Slim Bean, C-ROM Mix and Baked Blacjbean7 obtaining the same behaviour.
Important: I'm restoring around 54 apk using Titanium backup (games, applications and utilities) in every case. I did not tested the ROMs without these restorations.
Click to expand...
Click to collapse
This is the problem I am having. I can see internal sd card on CWM.
But on booting in android, whatever the rom is , does not mount internal sd card on booting android.
Please help to solve this.
Same here
TheMask007 said:
This is the problem I am having. I can see internal sd card on CWM.
But on booting in android, whatever the rom is , does not mount internal sd card on booting android.
Please help to solve this.
Click to expand...
Click to collapse
I have been reading/researching about this issue for about a week (on and off) trying various fixes because this is driving me bonkers.
I have tried:
1) Reduced the amount of used space on my SD Card (Samsung 16gb SDHC) to half
2) Moved as many apps as I can to SD (Noticed more frequent unmounts after this)
3) Removed my Nandroid Back-up from my SD
4) Reflashed CM 10.1
The last thing I am going to try is wiping/reformatting my SD card. If that fails then im suspecting something else is happening at OS/kernel level. I have read in other forums where people have tried a full wipe and restore apps slowly but still get the same unmount. One user has tried another SD card (smaller 4GB one) which seemed to solve their issue?? Weird.
Anyway, I will report back if I have any joy.
In your kernel settings you have the option to mount/unmount system and more or you could write/download a script that mounts the sd card automatically.
Maybe this could help: http://forum.xda-developers.com/showthread.php?t=1971689
I give up.
cixty said:
In your kernel settings you have the option to mount/unmount system and more or you could write/download a script that mounts the sd card automatically.
Maybe this could help: http://forum.xda-developers.com/showthread.php?t=1971689
Click to expand...
Click to collapse
I tried it and no good. It seems as though the Internal SD is mounted, but some error is causing it to operate/display as unmounted via OS.
I completed more testing (extreme):
Wiped Internal SD
Wiped External SD
Try other kernel
Try other CM based ROM
The issue still occurred.
I then reinstalled Stock (XXJVT) via ODIN (Pit 512) and Semaphore kernel to see if its a hardware thing.
Nope.
This combo works amazingly. Infact its faster, smoother and easier to use (along with additional tweaks in Semaphore) than CM10 so I wont be going back to Jelly Bean on this phone. Ever.
Gingerbread for the win!
Hi,
I am using PAC-ROM v22.2 (Jelly Bean) and have the same problem: 80% boot don't mount the internal sdcard (I have no problem with the external sdcard). I can't even mount it manually as xalo2k does, cause I have no "Mount SD Card" menu under Settings/storage.
I spent many hours trying to search for a fix on google, xda, and others with no success. I found a lot of "litterature" on how to mount the sdcard on the PC, or how to swap internal and external cards. However, I don't care about mouting my sdcard on the PC, and I don't want to make believe Android that my external sdcard is the internal one, as I would not like to loose the internal 8GB that the phone is supposed to provide.
In Terminal Emulator, I can do:
> su
> mount -r -w -t vfat /dev/block/mmcblk0p1 /storage/sdcard0
> cd /sdcard
> ls -l
There I can see my files. However, if I exit root, the files don't appear anymore. Hence this looks like a permission problem.
Unfortunately ESExplorer still tells me sdcard0 is not mounted, and my apps (i.e. the camera) aren't able to access it. Additionnaly, the apps I had moved to the sdcard are'nt accessible...
So I tried to fix the permissions. Going under /storage as root, I can see:
drwx------ root root 1970-01-01 01:00 sdcard0
d---rwxr-x system sdcard_rw 1970-01-01 01:00 sdcard1
Si I try:
> busybox chown -R system:sdcard_rw sdcard0
But I get "Operation not permitted" for each dir/file in sdcard0
How comes that an operation is not permitted to the root user ???
Did anyone fix this problem ?
Edit: "You can't chown or chmod a vfat partition let alone a directory within it. You can only change ownership and permissions in fstab and it will apply to all directories and files. So to change ownership of the entire mount point you would change your fstab entry" (see http://ubuntuforums.org/showthread.php?t=1646849)
Thanks and regards
OK guys, I finally found a solution.
Thanks to http://ubuntuforums.org/showthread.php?t=1646849 I mentionned just above, I decided to write an fstab file (the name is important) and placed it under /etc:
/dev/block/mmcblk0p1 /storage/sdcard0 auto rw,uid=1000,gid=1015,fmask=0702,dmask=0702 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Basically, this script is the result of the terminal command (you need to be root):
mount | grep sdcard0 > /etc/fstab
... which I ran after I could get the sdcard mounted (after a mount on PC and eject). But it first failed with errors on options, so I removed a few of them until I kept the lines above.
Then I wrote a little script which I place on my external sdcard which does not have a mount problem at boot:
busybox mount -a
and placed a shortcut to this script on my desktop with SManager.
I just have to click on this shortcut after boot and the internal sdcard gets mounted.
I tried to place this script under /etc/init.d with the hope it would be launched automatically at boot, but this did not mount the sdcard. If anyone knows why ???
Hope this helps !
Well... still having troubles with my sdcard... With the above fstab script I can mount it, access the files, etc...
However, the camera still asks me to insert a sdcard... Is this a permission issue ? Which permissions (owner, group, etc...) does the camera need ? My DCIM dir has the following permissions:
d---rwxr-x system sdcard8RW 2013-06-04 10:36 DCIM
Thanks and regards
- Regis
Hi guys,
This is my first post here, because this is the first time I’ve encountered a problem where I can’t find a solution for on the forums and or random google searches. So I decided to make this thread for myself and others that can’t find the solution to this problem.
So basically this is (I think) the main problem
The internal sd card of my Galaxy S GTI9000 is corrupt.
I can only read the files that are stored, when I try to write (copy a file, delete files or format the whole internal storage) the changes only have effect until the internal sd card is remounted.
This does let me think the internal sd card suddenly became write-protected.
The tricky thing is to know if this can be resolved or if this is truly a hardware problem.
I personally think making the external sd card the internal sd card could work.
What I’ve done so far
Running fine on Slimbean 2.2 until one day it suddenly was in Recovery mode; bootloop
- Reflashed with Slimbean 2.2; bootloop
- Wiped and reflashed; bootloop
- Wiped and flashed CyanogenMod 9.1.0; starting but encryption unsuccessful
- Wiped and flashed CyanogenMod 10 Build 20120920; bootloop
- Flashed 2.3.4_I9000XXJVP; starts fine but apps are crashing all the time
Here I discovered the internal SD Card writing problem
Flashed several official firmware versions with same outcome as the point above
Errors encountered while flashing these firmwares (not always):
- E:format_volume: rfs format failed on /dev/block/mmcblk0p2
- E:format_volume: rfs format failed on /dev/block/stl10
- E:format_volume: rfs format failed on /dev/block/stl11
Firmwares flashed
- I9000XWJS5 (JS5_JS3_JPY_ tar)
- I9000XWJW5_I9000XENJV6_XEN (JW5_JV6_JW4 tar)
- JW6_JW5_JW4 tar
- I9000XXJVT
Also tried
- Hard reset in JVP (gave errors mentioned above)
- Use external sd as internal sd (didn’t succeed in doing this)
- http://forum.xda-developers.com/showthread.php?t=1188482
(got stuck at repacking kernel, same as OP of that thread)
Best I could do
What works the best for me right now is flashing JVP, but:
:good: Can make calls
:good: Can send text messages
Apps are crashing often
No Wi-Fi
No mobile internet
Can’t get root access (with CF-Root)
I hope you can help me, thanks in advance.
-UPDATE-
I did this workaround: http://forum.xda-developers.com/showthread.php?t=1906089
Now I have a fully working phone again, but still the same problems with the internal sd card. (can still be accessed)
If you have the same problem and also have a external sd card the workaround mentioned above would definitely work!
Thanks to reganstott
Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????
Did you format it to fat32? In recovery did you try formating the external storage?
diaboliko.hacker said:
Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????
Click to expand...
Click to collapse
*bump
I'm facing the same problem right now. It occurred after I did a hard reset. In the best case scenario, this is just a partition table corruption, but in the worst, a physically damaged card.
On Linux, I have fixed partition tables with a nifty tool called gpart (not gparted). There is a similar utility available for Linux, Windows, Mac etc. called TestDisk. Unfortunately, these tools are not available on Android. However, there is something called aparted available on Play Store that supposedly fixes filesystems.
I have installed it, but it wants to install some browser addons too. I've tried to repair the filesystem that it shows as empty, but no luck so far. I will shortly check its online manual, but I hope we can get something like gpart on Android.
diaboliko.hacker said:
Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????
Click to expand...
Click to collapse
Hi, I have been able to get the Internal SDCard (/storage/sdcard0) mounted again, albeit with loss of data. Look at my recent post http://forum.xda-developers.com/showpost.php?p=48595569&postcount=24
and the one from which I got the hint
http://forum.xda-developers.com/showpost.php?p=35726016&postcount=6
The step by step procedure is here: http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
but if you have only one partition damaged, you could just check it with e2fsck and then, if necessary, recreate it with mkfs.exfat or the other method in the referred post.
EDIT: link to parted and other files: http://forum.xda-developers.com/showpost.php?p=38598228&postcount=4
http://www.droidforums.net/forum/htc-droid-eris/78650-internal-storage-partitions-screwed-up.html
I don't know if you can recover your original data - I had tried formatting the partition, by mistake, to ext4 with mke2fs. You could avoid this, and see if you can back up your partition with dd before re-formatting it to fat32.
solved, I download latest frimware, and flash it throught odin and all are fixed
Hello,
I have got a samsung p1000 tablet from my friend, that it does not boot, there is no warranty for it, and he doesn't need this anymore. I googled what is its problem, and the internal sd was corrupt. I followed tutorials to open the tablet, got off the internal memory which stored the data and the cache partition, then put everything back. After many tries,reflashes, bricks, etc, I got to this solution: I flashed the stock t-mobile firmware with odin 3.07 (this version ignored fail of movinand.rfs and hidden.rfs, not like earlier versions, like 1.85), installed overcome kernel, went to recovery, edited the /system/etc/vold.fstab file and partitioned the sd card as it needed. I booted and it worked, the android system ran from the sd, and the sd's 4gb fat32 partition was used as "internal" sd. I did it by this tutorial: http://forum.xda-developers.com/showthread.php?t=1463756& My partitions are:
1. Primary, fat32, ~5400mb (sdcard)
2. Primary, ext4, 2000mb (data, so applications' place)
3. Primary, fat32, 100mb (preload, or cache?)
OK. It's 2014, I cannot stick with gingerbread. I installed the official cm11 kitkat (http://download.cyanogenmod.org/?device=p1), but it had a problem, after searching i found it:
I can't use camera, cannot download anything and cannot open sdcard0 because: sdcard's fat32 partition is mounted as sdcard1. In KitKat, fstab file (fstab.p1) is in the root. I have to do one of these, but I cannot:
- unpack boot.img then edit fstab.p1 file, repack and reflash it, to use as sdcard0. simply modifying it does nothing, it changes itself back, and sometimes causes a bootloop.
- this solution, that I don't understand: http://forum.xda-developers.com/showpost.php?p=52931787&postcount=118
I'm pretty much confused, because it worked in gingerbread, but it had fstab in other folder, had an other structure of it, it was touchwiz, not cyanogenmod, etc.
Adb logcat and file manager both say: permission denied to sdcard0, ok, because it has been got out by me, but I don't need sdcard1, only sdcard0.
I would appreciate any help from you guys, telling me how to do one of these solutions, which would work and be the better for this case.
(i know this tab is old and obsolete, but it would be good for me for youtube, movies, xda, some games, just for home )
Same problem
I am having the same damn problem. I'm not a developer, and I'm using cygwin, but I do want to poke around in boot.img. How did you unpack it? I was getting an error involving magic android header or something. Also is there an fstab in the recovery? Should I flash that with heimdall, and push edited rom? Thanks for any help, and if you figure it out please post.
bluesnaketree said:
I am having the same damn problem. I'm not a developer, and I'm using cygwin, but I do want to poke around in boot.img. How did you unpack it? I was getting an error involving magic android header or something. Also is there an fstab in the recovery? Should I flash that with heimdall, and push edited rom? Thanks for any help, and if you figure it out please post.
Click to expand...
Click to collapse
I wasn't able to unpack it in cm11 rom. It says the same, there is no magic android header.
I am able to do the following:
DOWNLOAD MODE (turn off, volume down + turn on)
RECOVERY MODE (turn off, volume up + turn on)
- Format 16g memory card like this (e.g. with miniTool Partition): | sdcard,primary,fat32,~5000mb | data,primary,ext4,~1800mb | preload,primary,fat32,~200mb |
(with bigger cards, obviously bigger sdcard and data partition)
- DO NOT format sd with inserted in tab, and mounted in recovery; it will make partitions INSIDE of mmcblk0p1 block, not 3 blocks, mmcblk0p1, 0p2 and 0p3. So, DO format like in laptop, with microSD>SD transformer
- Insert SD card to TAB
- Flash gt-p1000_mr.pit and GB_Stock_Safe.tar with odin 3.07 (the only one which can push hidden.rfs, or skipping it automatically, like ignoring it in heimdall)
- Reboot in recovery mode, see that it can't see int. memory
- Reboot to download mode, flash overcome kernel
- Reboot to recovery, connect to adb, and now you can "adb pull /system/etc/vold.fstab"
- The file pulled to the adb folder should be edited to this (got this from a tutorial):
Code:
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = disable
format_option = -r 1558
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = enable
}
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
#end line ## keep this line
- Now type in adb: "adb push vold.fstab /system/etc/"
- To check out booting, type in adb: "adb logcat".
- Reboot your device.
- A female robot voice tells you not enough space on system partition, converting it, estimated time 2 mins, etc etc.
- After a while you should see many-many lines written in adb window, and see your tab booting.
- When turned off charging for 1st time, don't worry, it will convert something again, female voice will appear again. Never so again.
- Now you have your tab working camera, sdcard, apps, etc.
STOP HERE? IF YOU WANT A WORKING 2.3, CONTINUE IF YOU WANT A HALF-WORKING CM11.
2.3 is outdated, I tried to update to cm11
- Go to overcome recovery
- Recovery detects sdcard0 and sdcard1 normally.
- (I didn't do any wipes )
- Flash cm11.
- It will reboot to clockworkmod recovery.
- NOW FCKN recovery detects external sd partition 1 (your savior) as sdcard 1, FUUUUU!
- You have to flash the zip file again.
- Flash gapps. Because of "missing" (it's just mounted in the wrong place) sdcard partiton, some of them can not install.
- Now system boots, you can install apk-s. But even if you umount and mount the sd in the good place, camera and market sd-required apps won't work. So like fb, messenger, circle don't need them, so they work. BADLAND, Real Racing, won't, they need the sdcard mounted in place by the fstab file. You cannot download files in stock browser, neither in Dolphin, only in CM Browser.
Choose, you want to use an older, working os, or a half-working, but newer os, with more (cm features)
Maybe I will include the programs I used, when XDA allows me to place links in this post.
still trying...
Thanks for the info. Maybe if I knew what to do with this http://forum.xda-developers.com/showpost.php?p=52931787&postcount=118 I could get somewhere. I'm still determined to get this to work properly. It worked in that old terenceng rom so there has to be a way...