Hello!
I am running rooted stock Android 2.3 on LG E405 (no working 4.x ROMs exist for the device)
I have two questions:
1) What is the shell command to manually make android allow the PC to mount androids' (internal) partition as USB-drive? (I cannot think of right keywords to google this one up - please help!)
2) How does android determine which partition is which (i.e. which one to remount for the PC when connecting in "USB storage" mode), beside vold.fstab and init.rc? On android 2.3 that info is not in "framework-res.apk", so where is it? In the partition table itself?
Please help me search the forums for an answer. ANY advise is much appreciated!
This is why I ask:
I had switched data partition with internal sdcard partition.
Here's how:
Phone had a very small "/data" partition on /dev/block/mmcblk0p21 and large internal "/sdcard" partition on mmcblk0p20
So I reformatted mmcblk0p20 (ex-sdcard partition) into EXT4 and mmcblk0p21 (ex-data partition) into FAT32
Then I changed init.rc to mount mmcblk0p20 as /data type EXT4 and mmcblk0p21 as /sdcard type VFAT (mounting /sdcard was commented out in stock init.rc for some reason). This required modifying my boot image.
I have also set correct partition number in vold.fstab:
[#]dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host[/#]
So basicly I now have a large /data partition and small internal /sdcard.
I'm able install up to a gigabyte of APKs and it works fine.
However, when I connect to my PC via USB into "USB Storage" mode, the phone seems to still try to unmount what was previously sdcard partition (/dev/block/mmcblk0p20), instead of what is NOW an sdcard partition (/dev/block/mmcblk0p21)
I can still send files to the phone via wi-fi and ADB, but the ability to mount it directly would be nice.
If I accidentally select "erase internal sdcard" from storage menu, that will also most likely erase what is now my /data partition, softbricking the phone.
The "factory reset" option will probably only corrupt the sdcard.
There may be other problems with that.
I am also interested in mounting the data partition in this way. Does anyone know how to do it?
Related
Can someone please explain to me how to correct is problem? I'm new to installing roms and rooting. I'm using clockwork.
No app2sd partition found. Skipping format of /sd-ext.
Get rom manager app from market and flash clockwork recovery, then partition your sd card to get an ext.
Or do this with amon ra recovery.
Sent from my HTC
Thanks for the advice. I been trying to install cyanogenmod 6 on my evo. Are there any specific setting of an 8g sdcard and do i still need to install a ENGbootloader if i partition my card?
No app2sd partition found. Skipping format of /sd-ext.
--Installing: SDCARD: /clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-supersonic-signed.zip
Finding update package...
Opening update package...
Installing update...
Welcome to Cyanogenmod-6.0.0-Supersonic!
assert failed: getprop("ro.bootloader") =="0.76.2000"
getprop("ro.bootloader")=="0.79.0000"
E: Error in /sdcard/clockworkmod/download/mirror.kanged.net/cm/stable/supersonic/update-cm-6.0.0-Supersonic-signed.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue
im having the same time of problem! help
Solution for No app2sd partition found. Skipping format of /sd-ext
Hi,
Background:
I have a beloved ZTE BLADE.
Had a new 8 GB Class6 microSD card.
I don't have external SD card reader!
Goal: To partition SD card with FAT32 and ext2 partition to use app2sd feature.
Problem: ClockWork 3.0.1.4 (CW) can't do partitioning. (Exactly it say it is done, but after it can't find ext partition.)
Message is: No app2sd partition found. Skipping format of /sd-ext
Solution:
1. adb shell - (There are some guide for beginner how to do this.)
2. umount /dev/block/mmcblk0p1 (or else parted will crash. Also fdisk can't write partition table because of used partition on same device!)
3. fdisk /dev/block/mmcblk0 partition to fat+ext2 Don't forget to write it at end!
4 Manually make ext2 fs:
#mkfs.ext2 /dev/block/mmcblk0p1
5. Manual mount of ext2 partition. ( Or else you will faced with error message later. CW will not se the EXT2 partition !!! )
Error message if you skip this step:
No app2sd partition found. Skipping format of /sd-ext.
# mount /dev/block/mmcblk0p2 /sd-ext
6. Umount ext.
# umount /dev/block/mmcblk0p2
Tadamm! Voala...
CW will be able to format EXT partition and mount it.
The trick was manual umount FAT partition + manual mount ext2.
Regards,
Robert Szabo
No known solution (so far) for Nook Color
This weird problem is showing up when I am using Clockwork to prepare my Nook Color for installing an Android installation. It is appearing pretty consistently right now.
I have looked at various solutions:
1. Creating an ext partition on the SD card
This involves going to the Advanced selection on Clockwork and partitioning the SD card. This is a bad idea, because it (obviously) wipes the SD card completely, removing Clockwork and making the SD card un- bootable. As a result, you cannot do anything else with Clockwork (including, of course, any flashing!).
2. Attempting to create an app2sd partition on the Clockwork SD
I noticed that the Clockwork image, when placed on an 8 GB SD card, leaves about 380 Mb of unallocated space. Using EASUS I attempted to allocate some space for a partition called "app2sd". I do not know if this would have solved the problem, because ASUS is unable to create the partition. When you do the Apply in EASUS, it acts like it is creating the new partition, but then it reverts everything back to unallocated.
3. Searching for solutions on the Net
This is a waste of time, because most of the solutions people have given are either not for SD cards with Clockwork on them, or they presume that you already have a flashed and running installation and suggest using an installed Clockwork in order to create the partition. Since I am trying to get it to work properly on a Clockwork SD, these solutions do not help.
What is needed is either a Clockwork installation procedure that places an app3sd partition on the SD card when the image is put on, or a way to place an app2sd partition on the card after the Clocwork image is put on it.
This of course assumes that the app2sd partition is even needed on the Clockwork SD. If it isn't, then could somene please tell me so that I ccan forget about this problem?
Otherwise, does anyone know of a way to get this partition on a Clockwork SD card?
Thanks in advance for any information...
before putting the ROM preferred to do this: put the original CWM / + volume buttons and power / do 2 wipe / replace the modified CWM / do the other 2 in advanced wipe / format system / install the ROM favorite / and you're ok .
* doing so I have solved this problem.
Just installed link2sd earlier (formatted partition as ext3). Wanted to flash a different rom. Trying to backup my phone, and clockworkmod tells me it can't mount sd-ext. Anyone know a reason and/or work around?
I think CWM works only with ext4 partition AFAIK. So, you can re-partition your sd card to a ext4 partition using CWM, or you can format the ext partition only to ext4 using a computer.
YouArePoop said:
Just installed link2sd earlier (formatted partition as ext3). Wanted to flash a different rom. Trying to backup my phone, and clockworkmod tells me it can't mount sd-ext. Anyone know a reason and/or work around?
Click to expand...
Click to collapse
which version of CWM have you got?
3.0.2.4, which I've used for a while now, always tries to back up my 6GB ext2 debian partition unless I remember to change cards first. no way I leave room in the vfat partition to back up that much data.
I'll put it up on 4shared if you want it.
mihir287 said:
I think CWM works only with ext4 partition AFAIK. So, you can re-partition your sd card to a ext4 partition using CWM, or you can format the ext partition only to ext4 using a computer.
Click to expand...
Click to collapse
Guess when I get home I'll copy the contents to computer, reformat, and copy back. Hopefully link2sd will notice the formatting has changed and reset itself
Sent from my LG-VM670 using XDA App
Doesn't work with extra either. Version 3.2.0.1 I believe it was.
Guess it doesn't really matter, can just use titanium since its all app stuff on there anyways...
Sent from my LG-VM670 using XDA App
i use CWM to back up my 512MB ext2 partition for my data2ext all the time (with the rest of the backup) and it seems to have no problem, and just to check i just mounted the partition in mounts and storage and it mounts fine. I know some recoveries ive used in the past on other phones would have problems with partitions that were not in 64-128-256-512-1024 MB, etc. format because of block size issue errors that i would get (when mounting or trying to set block size to 4096). I also found that when partitoning/formatting to ext2/3/4 some programs do not properly write the drive formatting and certain systems/recoveries/apps could not properly read them on the android. the best most consistent (android friendly) formats that i have gotten to date were in ubuntu (or any other) linux using "gparted". It seemed to always be the best and usually better than the format done by the phone recovery. Hope this helps. Sorry to drone on and on.
Partitioned originally with gparted. Have since resized to be 2048, and set its label to 'sd-ext'. Now instead of getting an error saying sd-ext might not be supported on my device, it just gives me a generic 'error mounting sd-ext'
I've had ext partition mounting problems before, I'm not sure if the cause is something to do with vold or what, but
after unmounting a sd card to exchange it with another one, it changes the device partitions in /dev/block like
/dev/block/mmcblk1p2
for the sd-ext partition instead of the normal
/dev/block/mmcblk0p2
you can see if this has happened by
Code:
ls /dev/block
in adb shell.
to mount it manually, if the numbering is off,
Code:
mount /dev/block/mmcblk1p2 /sd-ext
I've only had this happen with android running, but it might work in recovery too
Switched over to using data2ext. Mounts the 2nd partition as the /data partition instead of /sd-ext. Can manually mount 2nd as /sd-ext from within rom, but it doesn't carry over to recovery.
A possible solution... Create a symbolic link pointing /sd-ext to the 2nd partition? But then again, since /data now points to 2nd partition, is recovery picking up on that unknowingly and backing up the 2nd's contents when it thinks its backing up the normal /data?
I suppose I should investigate.
Edit: Yep it does backup the 2nd partition, thankfully. Just tried to install a theme made in UOT Kitchen, it borked some stuff, and the restore worked.
My situation: Galaxy S3 with latest (26 Oct. 2012) update to 4.1.1 via Kies. Then rooted. Works smoothly. External Sd-card visible, no problem.
Then:
repartitioned SD-card with gparted in Fedora machine: mmcblk1p1 with old contents, mmcblk1p2 for new contents, both vfat. Filled mmcblk1p2 with contents from linux machine.
In the phone the first partition (the one with the old data) is recognised as before. The second partition is not seen.
By using the terminal emulator as super user I can mount the second partition by the command:
mount -rw -t vfat /dev/block/mmcblk1p2 <mountpoint>
<mountpoint> is a directory VISIBLE to File Explorer.
After mounting, however, the directory contents are NOT visible in File explorer (even after stopping and restarting File explorer) but can be listed perfectly in the terminal emulator. Giving the cp-command for copying of an individual (MP3) file from the <mountpoint> to the folder Music shows the copied file in that folder and the music can be played in the usual way through the GUI.
Question:
Does anybody have an idea how to make the mounted 2nd partition visible to the apps so that the files can be accessed though the GUI?
Thanks for thinking about this problem.
Bananiel-1944
Found the solution by some more thinking after all:
mount -rw -t vfat -o umask=0000 /dev/block/mmcblk1p2 <mountpoint>
The -o umask=0000 is essential, otherwise the permissions are rwx------; with the umask option they are rwxrwxrwx and thus can be reached.
For safety sake, mount when needed and umount promptly afterwards.
Bananiel-1944
Bananiel-1944 said:
My situation: Galaxy S3 with latest (26 Oct. 2012) update to 4.1.1 via Kies. Then rooted. Works smoothly. External Sd-card visible, no problem.
Then:
repartitioned SD-card with gparted in Fedora machine: mmcblk1p1 with old contents, mmcblk1p2 for new contents, both vfat. Filled mmcblk1p2 with contents from linux machine.
In the phone the first partition (the one with the old data) is recognised as before. The second partition is not seen.
By using the terminal emulator as super user I can mount the second partition by the command:
mount -rw -t vfat /dev/block/mmcblk1p2 <mountpoint>
<mountpoint> is a directory VISIBLE to File Explorer.
After mounting, however, the directory contents are NOT visible in File explorer (even after stopping and restarting File explorer) but can be listed perfectly in the terminal emulator. Giving the cp-command for copying of an individual (MP3) file from the <mountpoint> to the folder Music shows the copied file in that folder and the music can be played in the usual way through the GUI.
Question:
Does anybody have an idea how to make the mounted 2nd partition visible to the apps so that the files can be accessed though the GUI?
Thanks for thinking about this problem.
Bananiel-1944
Click to expand...
Click to collapse
Dear Bananiel,
your post was closest to the solution of my problem, maybe you could suggest something that will finally help me.
I've partitioned external SDcard with CWM to be used for Link2SD. Link2SD's script works fine and the EXT2 partition mounts well. The problem is with the FAT32 partition which can't be mounted by android (I get "SD card empty of file system damaged" in the notification area). When I go in CWM recovery mode I can mount that partition by choosing "mount USB storage" option and then I can see it on my PC. Partition is healthy and PC has no problems with it.
I've tried issuing commands you've suggested in your post through ADB SHELL, after that when I go to folder that I've designated as mount point I can see files from non-working partitio, but the message in notification area still persist. Also the change is not permanent, after reboot I have to do that again.
Thanks in advance for any help given.
Bananiel-1944 said:
Found the solution by some more thinking after all:
mount -rw -t vfat -o umask=0000 /dev/block/mmcblk1p2 <mountpoint>
The -o umask=0000 is essential, otherwise the permissions are rwx------; with the umask option they are rwxrwxrwx and thus can be reached.
For safety sake, mount when needed and umount promptly afterwards.
Bananiel-1944
Click to expand...
Click to collapse
dxage said:
Dear Bananiel,
your post was closest to the solution of my problem, maybe you could suggest something that will finally help me.
I've partitioned external SDcard with CWM to be used for Link2SD. Link2SD's script works fine and the EXT2 partition mounts well. The problem is with the FAT32 partition which can't be mounted by android (I get "SD card empty of file system damaged" in the notification area). When I go in CWM recovery mode I can mount that partition by choosing "mount USB storage" option and then I can see it on my PC. Partition is healthy and PC has no problems with it.
I've tried issuing commands you've suggested in your post through ADB SHELL, after that when I go to folder that I've designated as mount point I can see files from non-working partitio, but the message in notification area still persist. Also the change is not permanent, after reboot I have to do that again.
Thanks in advance for any help given.
Click to expand...
Click to collapse
In my situation (SD-card with two partitions, both vfat) the first partition automatically was mounted at start-up, the second needed to be mounted manually whenever I wanted to access it. This was also my intention as that second partition contains sensitive information.
Android has a file fstab.<system-id> in the root directory, in which some mounts are mentioned (but not all).
You could try to edit this file with the permanent mounts you are looking for. I'm not sure if that works, however, as I do not want a permanent mount.
Can you publish your results, please?
Bananiel
Finally!
I managed to get my external partitions visible with the help of this post.
Device: Samsung Galaxy Tab2 10.1
ROM: Candy5_p5110 Android 5.1.1
SDExternal: 2 Partitions; 1st VFAT, 2nd Ext3
Using Mount2Sd from Google Playstore.
I had the same mounting issues. SD external would only mount Partition 1 automatically and manually mounting Partition 2 would only be visible via Terminal.
The solution that finally fixed the invisible 2nd Partition was to reformat the 2nd Partition with Ext3 and allowing Mount2Sd to find it and mount to /sd-ext. Formatting to vfat or ext4 did not work. Only Ext3 did the trick.
I hope this helps others and big thanks to the OP for bringing this issue up.
Hi,
I have a client's tablet that shows up with "0.00 mb" of free internal storage. The device is not rooted but I can flash the device through standard recovery. Unfortunately completely re-flashing the device isn't an option.
I tried moving busybox from /system/xbin to /system/bin but that did not help.
I checked mount, and /data is not mounted. Is there some kind of check I can perform?
What are reasons why the data partition is not mounted from one day to another?
I can't find a file like /dev/block/mmcblk0p8 or similar that I could try to mount.
Any ideas what I can try?
thanks for your help,
Jan
Bump and additionally:
What app (on a non-root tablet) could possibly corrupt the data partition so that /dev/block/data is gone?
Best regards,
Jan
Hi,
after flashing a custom ROM which did not work as expected, I got "E: unable to mount ..." errors.
After investigating I formated the preload and mounted preload manually in the recovery.
Somehow my SCARD now shows additional "/0" in the path to the data, leading to data being unable to be found.
e.g. to the download folder is now located in SDCARD/0/0/0/DOWNLOAD.
I assume this happened when mounting the preload or other folders maually?!
How can I get this back?
I do not tink this is realted to any ROM or device, but I am on OMNIRom 4.4.4, CWM 5.5., GTAB 7510 Wifi
Thanks
xdatroxx
"Preload" seems to be A system partition, secondary for preloaded system apps, so you really should not be mounting that to SDCARD (internal storage) unless it's unused by the roms and you know what your doing/want that partition for personal use.
If the rom gave you that error(unable to mount..) right after installing it then I would not recommend the ROM.
Can you access SDcard eg. use the files?
sdcard should normally be seen as:
/sdcard
or:
/storage/emulated/0(or legacy)
you can mount the partitions correctly but you have to find the right partition layout for your gtab.