How the heck do I mount my ext2 partition?
I have an lg stylo (t-mobile) rooted
My system dirs are all under various mmcblk0p#s
My ext sd is either mounted under mmcblk1 mmcblk1p1 or mounted via mount device by name script
All I want to do is get my ext2 partition mounted and visible.
Any help would be highly appreciated.
Related
Add these two zips I quickly put together to swap between 3.0.0.5 and 3.0.1.0 recovery on the same SD Card. This way if you want to test images for 2.2 Froyo you can quickly turn your SD into 3.0.0.5 and if you want to test for CM7 you can flash to 3.0.1.0 on the fly!!!
If you have any questions just ask. Please limit your questions to ONLY this topic.
xboxexpert said:
Add these two zips I quickly put together to swap between 3.0.0.5 and 3.0.1.0 recovery on the same SD Card. This way if you want to test images for 2.2 Froyo you can quickly turn your SD into 3.0.0.5 and if you want to test for CM7 you can flash to 3.0.1.0 on the fly!!!
If you have any questions just ask. Please limit your questions to ONLY this topic.
Click to expand...
Click to collapse
I would think once you have 3.0.1.0 then you should be all set for 2.2 (ext3 FS) or CM7 (ext4 FS) as 3.0.1.0 supports both while 3.0.0.5 only supports ext3 thus why it won't work with CM7 as has ext4 FS...
Perhaps I'm mistaken when you say CWR 3.0.1.0 recovery for SDcard... I'm thinking you want this to write to SDcard??? If so then this seems wrong... your uRamdisk has /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p5 NULL ext3
/data ext4 /dev/block/mmcblk0p6 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3
This will write to EMMC Not SDcard... to have recovery write to SDcard you need this file to be;
# CWR 3.0.1.0 SDcard uRecRam: /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk1p2 NULL ext3
/data ext4 /dev/block/mmcblk1p3 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk1p4
/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p4 NULL ext3
If you are just making an Sdcard that can be used to install to EMMC then sorry for commenting... but this is available in a number of different places while CWR 3.0.1.0 for Sdcard installs still doesn't exist thus why I was looking for someone to replace that file a couple days ago...
jtbnet said:
Perhaps I'm mistaken when you say CWR 3.0.1.0 recovery for SDcard... I'm thinking you want this to write to SDcard??? If so then this seems wrong... your uRamdisk has /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p5 NULL ext3
/data ext4 /dev/block/mmcblk0p6 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL ext3
This will write to EMMC Not SDcard... to have recovery write to SDcard you need this file to be;
# CWR 3.0.1.0 SDcard uRecRam: /etc/recovery.fstab
# mount point fstype device [device2] [fstype2]
/boot vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk1p2 NULL ext3
/data ext4 /dev/block/mmcblk1p3 NULL ext3
/cache ext4 /dev/block/mmcblk0p7 NULL ext3
/emmc vfat /dev/block/mmcblk1p4
/sdcard vfat /dev/block/mmcblk1p4 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p4 NULL ext3
If you are just making an Sdcard that can be used to install to EMMC then sorry for commenting... but this is available in a number of different places while CWR 3.0.1.0 for Sdcard installs still doesn't exist thus why I was looking for someone to replace that file a couple days ago...
Click to expand...
Click to collapse
If you put these files on a SD card and boot to lets say 3.0.0.5 and flash the 3.0.1.0 it will write the files to the SDCARD and your sdcard will now boot into 3.0.1.0 recovery and you will have a 3.0.1.0 sdcard. Let me know if you understand. I think i'm explaining it correctly.
So just to be clear and state the obvious - these zip files update the recovery version on the bootable SD card and do not write anything to the eMMC recovery area. Is that correct?
faceman66 said:
So just to be clear and state the obvious - these zip files update the recovery version on the bootable SD card and do not write anything to the eMMC recovery area. Is that correct?
Click to expand...
Click to collapse
Yes I believe you are correct. Place both files on the recovery SD and when you want to flash with 3.0.0.5 for like he said "FROYO" , just flash the 3.0.5.0.zip and it will replace the recovery kernel and ramdisk. And when you feel like flashing CM7, just flash the zip for 3.0.1.0 and "vice versa" as xboxexpert said.
xboxexpert said:
If you put these files on a SD card and boot to lets say 3.0.0.5 and flash the 3.0.1.0 it will write the files to the SDCARD and your sdcard will now boot into 3.0.1.0 recovery and you will have a 3.0.1.0 sdcard. Let me know if you understand. I think i'm explaining it correctly.
Click to expand...
Click to collapse
Okay... so you are putting standard CWR 3.0.1.0 on the sdcard that can then be used to flash updates to EMMC as defined by your recovery.fstab... I guess the point being for folks who don't want flash CWR directly on EMMC so as to retain stock recovery...
CM10 recent install from CM9, which was Encrypted for work email.
Read that you can just format the partition and it will install new roms fine.
Within CM10 I can see /ExtSDCard/ and but /SDCard/ aka /emmc/ in CWM wont mount.
Going further down into CWM, emmc wont mount so it looks like it has installed the rom fine as it boots without a physical SD Card inserted? When trying to mount /emmc/ the log shows the following error "Failed to mount /dev/block.mmcblk0p11" which I assume is related.
I would like to mount and format the previously encrypted internal storage, so It could be used as /sdcard/ in CM10 so apps like Camera would work.
Thanks
Edit: Fixed English
Edit: Ok so I have worked out its /dev/block/mmcblk0p11 - cant format it ext4 then mount it using "mount -t ext4 /dev/block/mmcblk0p11 /emmc" but all the 'scheduled' tasks still think its vfat, so as a work around ill just format it as vfat.
This should be easy.... right?
busybox mkfs.vfat /dev/block/mmcblk0p11
Error:
mkfs.vfat: lseek: Value too large for defined data type
Ugh. Help me format this as vfat please
Fixed!:
Had to push a new version of busybox, which allowed vfat over 1gb.
Thanks me!
Hi,
Got this Desire Bravo with low internal memory so thought I should mount the app and data dirs to a ext4 partition on my SD card instead so I can install a lot of apps.
Followed this howto:
newton dot cx/~peter/2012/12/how-to-increase-app-space-with-a-partitioned-sd-card-on-an-htc-nexus-one-running-android-2-3-6-on-linux/
I found that my ext4 partition is mounted at boot time.
mount command gives the below:
/dev/block/mmcblk0p2 /mnt/sd-ext ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
I can copy the data to the ext4 partition without any problem using "cp -rlp /data/app /mnt/sd-ext/data" and "cp -rlp /data/data /mnt/sd-ext/data" .
I can see the data when doing a "ls /mnt/sd-ext/" - looks ok.
But after reboot the data is just gone - just dont get it. Grateful for any help for troubleshooting this.
Running ROM CM10.1_VJ_4.2.2_V6.3_May24 .
Thanks...
EDIT: installed S2E app (Simple2Ext) instead, which didnt work well, so tried Mount2SD instead and appears to be working OK.
I tried to install Link2SD in Micromax A58 as the internal storage is very low and need to install some more apps. Already rooted and installed Link2SD to use the ext4 2nd partition of my 8 GB SD card. After trying with all possible ways, couldn't get it worked. All the time it was showing error--
"Mount Script can not be created. Mount: No such file or directory"
Previously even the 2nd partition was not shown as mounted in the storage info of Link2SD but after modifying the install-recovery.sh in /etc path, the storage info now atleast showing the 2nd partition as mounted. My install-recovery.sh looks like below--
#!/system/bin/sh
/system/xbin/daemonsu --auto-daemon &
/system/etc/install-recovery-2.sh
mount -t ext4 -o rw /dev/block/mmcblk0p2 /data/sdext2
mount -t ext4 -o rw /dev/block/vold/179:2 /data/sdext2
Now, the problems are as below--
1) Installed multiple applications but none of them are actually linked to SDcard. The Link2SD shows them as 'On SD Card' and just after installing 9-10 small applications, the internal memory is now full. If I go to 'Create Link', it is giving error '/data/sdext2 mount not found'.
2) When try to recreate mount script and choosing 'ext4' as parameter, it still throws error
"Mount Script can not be created. Mount: No such file or directory"
It seems that even though the storage info shows the 2nd partition as mounted, but system couldn't identify it somehow. So, Link2Sd is not working at all.
Please help and advice further. Thanks a lot.
Hi Supporters,
there is a problem with my sdcard under Android 7.1.2 (root=true, adb=possible). The vFat Partition can be used, but the rest is not mounted and can not be used.
mmcblk1p1 vfat 183 GB Status : OK
mmcblk1p2 ext4 16 MB android meta Status: not mounted
mmcblk1p3 ext4 64 GB Status: not mounted (primary) (want to use that partition as adoptable Partition for extra internal memory)
mmcblk1p4 ext4 2 GB Status: not mounted (primary) (want to use that partition as SWAP Partition for extra RAM)
Trying to mount the Partition3 (64 GB) gives the error "mount: mounting /dev/block/mmcblk1p3 on /data/sdwyt2 failed: Invalid argument"
i have the apps "Apps2SD Pro" & "Link2SD" but they can't mount the 3 partitions too.
Does anyone know how i can mount and use the 3 ext4 partitions?
Solution: On devices running Android 7.0-8.1, file-based encryption (FBE) can't be used together with adoptable storage.
https://stackoverflow.com/questions...able-storage-not-available-on-device-with-nat