Hey folks,
I have recently replaced my older Evervolv on the Touchpad with a current Milaq Nightly, and for some reason it doesn't mount the internal SDcard partition (worked fine with Evervolv).
When I 'mount -t vfat /dev/mapper/store-media /sdcard' manually, it works fine and I can see the files in there, so the file system apparently is intact, but Android doesn't seem to recognize it as usable SDcard storage (i.e. no "move to SD" option in the app manager etc). The mount doesn't persist across reboots either, and adding an entry to /fstab.tenderloin is equally pointless.
Any hints on what could it be that prevents my device from automounting this partition?
WooShell said:
Hey folks,
I have recently replaced my older Evervolv on the Touchpad with a current Milaq Nightly, and for some reason it doesn't mount the internal SDcard partition (worked fine with Evervolv).
When I 'mount -t vfat /dev/mapper/store-media /sdcard' manually, it works fine and I can see the files in there, so the file system apparently is intact, but Android doesn't seem to recognize it as usable SDcard storage (i.e. no "move to SD" option in the app manager etc). The mount doesn't persist across reboots either, and adding an entry to /fstab.tenderloin is equally pointless.
Any hints on what could it be that prevents my device from automounting this partition?
Click to expand...
Click to collapse
It's not simply a matter of flashing the newer datamedia builds over an older, probably non-DM build. It requires restructuring the internal storage of the TP. Explicit directions are here. Use the newer version of the tool.
shumash said:
It's not simply a matter of flashing the newer datamedia builds over an older, probably non-DM build. It requires restructuring the internal storage of the TP. Explicit directions are here. Use the newer version of the tool.
Click to expand...
Click to collapse
The Evervolv before already was a datamedia build, and I have adjusted the partition sizes accordingly.
It worked correctly after the EW->Milaq migration about two weeks ago, and broke when I flashed a new Nightly over it last weekend.
(I did the whole cleanup via CWM before flashing the new nightly, just to avoid that question.)
Related
Hello.
Installed phiremod 4.1: http://forum.xda-developers.com/showthread.php?t=954902
All is fine, except one: I do not know how to access the internal data storage (5 GB).
A similar problem is described here: http://forum.cyanogenmod.com/topic/16812-internal-storage-media/
In fact, I typed in a terminal:
su
mount-o rw, remount-t rootfs /
mkdir / mnt / media
mount / dev/block/mmcblk0p8 / mnt / media
mount-o ro, remount-t rootfs /
... and the partition appeared, the mounted as "/mnt/media".
However, after rebooting the partition again is not visible.
How to correct this situation?
Thanks in advance.
Just a heads up, the internal storage is mounted on boot in the latest CM7 nightlies
Sorry, I do not quite understand.
Tell me please: fixes have already been made in the installation package "phiremod 4.4.1"?
I'm having the same issue as the folks above. I just installed phiremod V4.1 to emmc and it does not recognize all of the Internal Storage on the NC.
Apps > Settings > Storage shows Internal Storage at 0.92 GB, with available Internal Storage at 853 KB. No problems with the SD Card btw...it shows 7.4 GB.
I would really appreciate it if someone could point me to a post, or outline the steps required to flash the daily update of CM7 so that the current implementation of phiremod 4.1 with CM7 is able to recognize the full 5.00GB of Internal Storage?
Thanks in advance!
"Phiremod" is nothing more than a glossed over CM7 nightly, and an out of date one at that. From what i can tell, if you want to keep the "mod", there is no easy way to update to the latest nightly.
Becasue of the state of the build, with nightlys coming at us quickly, it is best to avoid these custom solutions all together.
The best i can tell ya, is to download the latest nightly, and start from scratch (format /system, /data, /cache **BUT NOT BOOT**). Because of the way the nightlys work, you WILL be able to flash a new one over the old, without losing data.
Perhaps it is too difficult for beginners.
I just tried to follow the installation instructions Phiremod V4.1 (see here: http://forum.xda-developers.com/showthread.php?t=954902).
After the problems with access to the internal partition, I installed the latest (nightly) build "CM7" (http://mirror.teamdouche.net/?device=encore), and problems with internal partition disappeared.
Nevertheless, Phiremod V4.1 was very convenient.
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
Loving the CM10 ROMs. Everything has been snappy on my nook since beta 2.
I thought I had the newer (revision 1.2+) nook partition layout (5gb data(apps)/1gb media). But now with CM10 I am getting an out of space error when trying to install new apps. I have moved all apps to my sd card and still get the error about not enough space. If I try and look at the partiton size it looks like it is maybe only 1gb now. Did installing a CM10 ROM change my partition size? Am I missing something else? Perhaps I am just wrong about my original partition sizes.
I searched some threads and the web and saw some discussion on my issue, particularly mention of a 'new CM10 partition layout', but this was confusing at best. It may not have even been nook related, but pertained to some phones.
dcahoe said:
Loving the CM10 ROMs. Everything has been snappy on my nook since beta 2.
I thought I had the newer (revision 1.2+) nook partition layout (5gb data(apps)/1gb media). But now with CM10 I am getting an out of space error when trying to install new apps. I have moved all apps to my sd card and still get the error about not enough space. If I try and look at the partiton size it looks like it is maybe only 1gb now. Did installing a CM10 ROM change my partition size? Am I missing something else? Perhaps I am just wrong about my original partition sizes.
I searched some threads and the web and saw some discussion on my issue, particularly mention of a 'new CM10 partition layout', but this was confusing at best. It may not have even been nook related, but pertained to some phones.
Click to expand...
Click to collapse
You can tell by looking in settings and storage. It will tell you the size of your media storage. If you truly have the 1Gb /data, you might want to look at Dean Gibson's repartitioning thread. He has a 2gb/4gb version.
And no, there is no repartitioning that cm10 does. That was for a phone you saw.
Sent from my Nook HD+ running Tapatalk
Well, I think I do have the 5gb data/1gb media partition layout afterall.
In Setting->Apps->Downloaded it shows at the bottom 'Internal Storage, 753Mb used, 4.2Gb free'.
If I launch a terminal window:
$ df /data
/data Size=4G Used=643M Free=4G Blksize=4096
$ df /emmc
/emmc Size=1G Used=83M Free=942M Blksize=4096
$ df /mnt/sdcard
/mnt/sdcard Size=15G Used=10G Free=4G Blksize=8192
I guess the only app that is giving me the out of space is Titanium Backup. I can't get it to install from either the appstore or from .apk that I downloaded. Both methods start installing and then say 'out of space'. I have been installing and removing other apps along the way with no similar problem.
I did wipe cache/dalvik cache when installing ROM. I also tried CWM Fix Permissions. I also tried CWM Backup -> Wipe Data/Factory Reset -> Restore.
Anyone know why Titanium Backup won't install?
dcahoe said:
Well, I think I do have the 5gb data/1gb media partition layout afterall.
In Setting->Apps->Downloaded it shows at the bottom 'Internal Storage, 753Mb used, 4.2Gb free'.
If I launch a terminal window:
$ df /data
/data Size=4G Used=643M Free=4G Blksize=4096
$ df /emmc
/emmc Size=1G Used=83M Free=942M Blksize=4096
$ df /mnt/sdcard
/mnt/sdcard Size=15G Used=10G Free=4G Blksize=8192
I guess the only app that is giving me the out of space is Titanium Backup. I can't get it to install from either the appstore or from .apk that I downloaded. Both methods start installing and then say 'out of space'. I have been installing and removing other apps along the way with no similar problem.
I did wipe cache/dalvik cache when installing ROM. I also tried CWM Fix Permissions. I also tried CWM Backup -> Wipe Data/Factory Reset -> Restore.
Anyone know why Titanium Backup won't install?
Click to expand...
Click to collapse
The only thing I can think of is some users are having read only problems on both SD card and /data, which is where apps get installed. Have you tried to install other apps since the TB install failed? A test you can try to see if you are one of the users with ro issues is to use a root file manager (there is one built into CM10 now) to create a test file somewhere on /data.
Sent from my Nook HD+ using Tapatalk
I'm attempting to format my external sdcard to ext2, just one single partition (no apps2sd magic).
The reasons are to have the ability to store >4GB files on the card, faster read times, and not needing compatibility with any M$ systems/PCs/Junk, journaling (>ext2) is not needed.
At the moment, I'm running a CM based ROM (cyanfox) and will likely try this out on a moto/stock based ROM after.
Here is my progress so far :
I'm able to mount the SD manually, though with some hoops being involved. The bionic will not mount it automatically, and is constantly telling me that it is unsupported/empty/needs to be formatted in the storage menu, and a permanent notification.
In a terminal shell, I can mount the device (/dev/block/vold/179:97) by specifying the type only as ext4. This is definitely not ideal, but I get errors when the type is specified as ext2 or ext3. (error : mount: Operation not supported on transport endpoint ).
At the moment, I've made an init script to mount the sd at /storage/sdcard1 but this doesn't cause android to think that the actual sd is mounted properly (empty sd notification still exists). Though it is at least mounted.
And I have edited the fstab file at root to change the sd type from vfat to ext2, but this file rewrites itself at boot. Unfortunately I'm not able to set an immutable bit on the file.. (android is not a type writer).
The ext2 filesystem has been checked for errors, does have files written to it, and is able to be read/written to in android after manually mounting it. Android just insists on a fat partition though.
Any help/tips would be appreciated. I'll update this thread in case anyone else would like to apply this as well.
Also, if I'm missing something blatantly obvious, please let me know
Perhaps someone can help. I've read a lot of the great content here but I've hit a wall.
A few weeks ago my ovation device was running cm11+cwm but began random rebooting. Clearing the cache+dalvik only helped briefly.
I tried an upgrade with a twrp 3.0.0.0 (using the amazing multiboot recovery SD), but it hung formatting the cache partition (I waited about an hour). Tried again, same thing.
I used adb shell to fix a blank file system type on the cache partition but was only successful in creating an ext2 partition there. I got cm13 booting but it trebuchet kept crashing. I tried twrp again and flashing a different image and tried a factory reset. Big mistake.
Now when I try to boot any recovery SD it doesn't boot all the way. Using adb shell, my dmesg shows that umount is hanging. No emmc partitions seem to be mounted. The partition data exists in dmesg but calls to parted hang. Mkfs.ext4 also hangs (naturally).
So I've lost the ability to fully boot recovery SDs (they are probably hanging when they try to mount the emmc partitions). As such I can't flash a recovery. I have a clockwork backup that has a system.ext.tar file in it, but I don't know how to use it at this point.
I can't mount /rom so I'm worried.
Is my emmc shot? Is there any way to tell?
Thanks!
Would a noEMMC SD be safe?
I guess what I was hoping to do was use adb to completely wipe and restore the device to a sane state, which would include repartitioning and formatting the emmc partitions. Is that possible? Maybe not at this point.
I guess another question would be: if my NookHd+ emmc is technically working but currently unrecoverable, is it possible for me to safely use a NOemmc SD card? There seem to be some warnings about those wrecking emmc but I can't find any technical explanation as to why.
Based on further diagnostics, my emmc is one of the faulty Samsung models and so I think the crashes and ultimate recovery failures were the failure of the emmc.
I've successfully installed 10.1 noEMMC on one microsd. Runs Okay but a lot of apps I am interested in don't work on android from this vintage.
I tried to install 4.4.4/CM11 noEMMC but it can't mount the necessary partitions as per the install process on the iamafanof Wordpress page. I also see SELinux errors in the twrp recovery log. Does anyone know how to overcome this mount issue that apparently impacts some people.
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Sorry to resurrect this thread, But it exactly speaks to my issue. You mention that the blk0 and blk1 devices need to be switched for cm11 image to mount partitions properly. Does anyone know specifically where this might be done. Can files of the existing nov4 cm11 image be altered to reverse these two devices?
CalculonsTalent said:
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Click to expand...
Click to collapse
Could you please teach me how to mount EMMC partitions and retrieve data specially /factory partition with ADB?
I can only boot my Nook HD+ with with bootable SD card with TWRP or CWM.
Thanks.