Related
I have Nookie Froyo on a 16GB SDcard and it's fairly stable. I do like to use the NC from the stock or rooted OS on the EMMC on occasion. When I'm running internal and insert the NF card, it only sees the boot partition just like under windows.
So, here is my thought. With Linux, it should be somewhat straightforward to have a script to unmount boot from sdcard and remount the SDcard partition on the SDcard as sdcard. The only similar thread I found was this one.
Can a bright person give me a hand on this one?
UPDATE: The answer lies here.
Homer
Homer_S_xda said:
I have Nookie Froyo on a 16GB SDcard and it's fairly stable. I do like to use the NC from the stock or rooted OS on the EMMC on occasion. When I'm running internal and insert the NF card, it only sees the boot partition just like under windows.
So, here is my thought. With Linux, it should be somewhat straightforward to have a script to unmount boot from sdcard and remount the SDcard partition on the SDcard as sdcard. The only similar thread I found was this one.
Can a bright person give me a hand on this one?
Homer
Click to expand...
Click to collapse
I lost the page but on the forums theres one talking about mount points. What you're going to want to do(or at least this is my guess) is run something like
Code:
adb shell umount /dev/block/mmcblk1 (This is the boot partition normally)
mkdir sdcard
mount /dev/block/"Whatever the sd card mount point is" sdcard
Try This
If you mean mouting the Nookie Froyo/Honey's sdcard partition, you can do it from a Terminal App. You just need to figure out what the Nookie card's mount device is and mount the 4th partition.
Try this:
Code:
(use cd command to non System Folder)
mkdir /nookie
su
mount '/dev/block/mmcblk1p4' '/(location of nookie folder)/nookie/'
This should Mount the Partition to the "nookie" folder. You shouldn't need to unmount the First partition. You just need to mount the 4th to a different location. Then use a File Browser like Astro or Root Explorer to Browse and Transfer files.
Then use this to unmount after done file transfers and stuff:
Code:
unmount '/(location of nookie folder)/nookie/'
Thanks for the replies. I think the goal here would be to make it transparent to applications that are writing to the sdcard partition. That way, I would browse to the files the same way regardless of the OS I happen to have booted. Also, the 117MB or so free on boot is going to fill up with junk and runs the risk of getting overwritten, wrecking the Froyo/Honeycomb installation.
Homer
More Suggestions
Homer_S_xda said:
Thanks for the replies. I think the goal here would be to make it transparent to applications that are writing to the sdcard partition. That way, I would browse to the files the same way regardless of the OS I happen to have booted. Also, the 117MB or so free on boot is going to fill up with junk and runs the risk of getting overwritten, wrecking the Froyo/Honeycomb installation.
Homer
Click to expand...
Click to collapse
Good point. How about this instead.
Code:
su
unmount '/sdcard'
mount '/dev/block/mmcblk1p4' '/sdcard'
This would unmount the boot partition and then mount the sdcard partition in it's place. This is assuming that Rooted Stock mounts the SDcard at folder '/sdcard' by default, I haven't rooted my NC's Stock.
Now Mounting the Media partition(Where your books and other Media are stored) from Nookie Froyo isn't as clear cut. I found the Mount Table for Rooted Stock and Media is listed different then the others. As shown in Bold:
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext2 ro,errors=continue 0 0
/dev/block/mmcblk0p6 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
[b]/dev/block//vold/179:8 /media vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0[/b]
As I said I don't have my NC Rooted so I can't investigate this. On the other hand, Accessing Stock System(p5) or Data(p6) partitions should be straight forward.
Code:
cd /sdcard
mkdir /stock-system
mount '/dev/block/mmcblk0p5' '/stock-system'
A few nights ago I set up my NC to dual boot following ...
http://forum.xda-developers.com/showthread.php?t=920347
Which in addition to stealing about 20% of the internal /media partition for the NF system, it also replaced the uboot to selectively choose which distro you wanted to boot from as well as editing the /system/etc/vold.fstab to change how the sdcard was mounted. Perhaps this last step may help(?)
BTW - I'm pleased with the dual booting off of the emmc. I'm a Linux person, so shrinking down the last partition and adding partitions 9 and 10 for FC seems like a nice, transparent solution. It doesn't seem to affect the operation of CWM's nandroid backup and restore (I've done both since dual booting) and I don't have to worry about popping out the SD card to boot the emmc based distro.
working on vold.fstab is the way to go..
Sent from my LogicPD Zoom2 using Tapatalk
samuelhalff said:
working on vold.fstab is the way to go..
Sent from my LogicPD Zoom2 using Tapatalk
Click to expand...
Click to collapse
This is exactly how its done on the honeycomb build floating around here.
Here is what the vold.fstab looks like in there:
Code:
$ adb shell cat /etc/vold.fstab
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1
## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
dev_mount sdcard /sdcard 4 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
#dev_mount media /media 8 /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
So this effectively mounts the partition 4 of the sdcard as /sdcard and everything works normally.
Mount NC Internal from Nookie Froyo
Ok I successfully mounted the Nook's Media Partition from within Nookie Froyo:
Code:
su
mount -o rw,remount -t rootfs /
mkdir /mnt/media
mount /dev/block/mmcblk0p8 /mnt/media
mount -o ro,remount -t rootfs /
NC Internal Media Partition is now mounted to '/mnt/media' as RW.
j4mm3r said:
This is exactly how its done on the honeycomb build floating around here.
Here is what the vold.fstab looks like in there:
Code:
$ adb shell cat /etc/vold.fstab
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1
## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
dev_mount sdcard /sdcard 4 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
#dev_mount media /media 8 /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
So this effectively mounts the partition 4 of the sdcard as /sdcard and everything works normally.
Click to expand...
Click to collapse
So I need to modify the vold.fstab on my emmc to mount the 4th sdcard partition as /sdcard. Let me get it up and running again and I'll give that a whirl.
Homer
Did some poking. This file does not exist in the default config. Should I create it with just this line:
dev_mount sdcard /sdcard 4 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
UPDATE: Nope... either need permissions set right or have to tell the system to look at the file.
Homer
Homer_S_xda said:
Did some poking. This file does not exist in the default config. Should I create it with just this line:
dev_mount sdcard /sdcard 4 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
UPDATE: Nope... either need permissions set right or have to tell the system to look at the file.
Homer
Click to expand...
Click to collapse
Hold on a sec... are you doing this when booting into the Nook rom? 'Cause if you are then just keep in mind that the Nook is based on Eclair and vold.fstab was introduced in Froyo...
The Idea that I was trying to convey was that in case you happen to be booting from a Froyo image on the SD card, then having such a seupt in the vold.fstab would allow you to mount the remainder of the SD card as /sdcard.
If however, you want to share the SD card partition when you boot into Nook, I'm afraid that this wont work. I think the Eclair vold is kind of dumb and always tries to mount the first usable partition off of the card, which'll be the small boot partition in case you have burned nookiefroyo.
On Eclair, change vold.conf..
Thanks again everyone! The answer is here.
Homer
seems on 1.2 editing vold.fstab works instead of vold.conf Just replaced the first 'auto' with 4 and poof, part. 4 is now the SD card!! Previously before 1.2 update vold.conf was the route. That didn't seem to work this time so once I edited fstab it was perfect.
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...
=================== GOOD NEWS ================
Thanks to GORO and Z we have a solution
tkymgr said:
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
Click to expand...
Click to collapse
Step by step guide
http://forum.xda-developers.com/showpost.php?p=16853029&postcount=39
thanks to waigsr
for those looking to see the technical aspects of it.
SE sample zip contains a vold replacement from cm7 which actually do the magic of making sure that first partition gets mounted.
Note : as Link2SD messes with install-recovery.sh its adviced that after flashing this zip port any specific tweak you have in install-recovery.sh over to install-recovery2.sh in the same folder.
and then run link2SD
Hope this helps.
-============== Keeping old study for later reference and memories only ==============
I have been messing around with Link2SD and its config here is a short writeup for those who want to help.
The basic problem
Link2SD looks for a partition no of /sdcard +1 partition
Android has a habbit of mounting the last partition as /sdcard
so link2sd is going to fail in all senses.
however if anything is mounting at /data/sdext2 Link2sd condsider it as a second partition
so we still have hope of using it however there are several limitations of it.
multiple ways in which link2sd could be used.
1) create 2 partitions on sdcard
a) ext2 partition as mmcblk0p1
b) vfat partition as mmcblk0p2
entry in install-recovery.sh
mount -t ext2 /dev/block/mmcblk0p1 /data/sdext2
Cons : xrecovery can't mount sdcard as its mmcblk0p1 that xrecovery mounts
2) create 2 vfat partitions
a) mmcblk0p1 mounting itself at /data/sdext2
b) mmcblk0p2 mounting itself as /sdcard
cons recovery related files will go in /data/sdext2
3) three partition layout
a) mmcblk0p1 -> reserverd for recovery related stuff
b) mmcblk0p2 -> link2sd
c) mmcblk0p3 -> SDCARD
or find an alternative to use mmcblk0p1 as /sdcard
or use a loop file as /data/sdext2
Do suggest what you all think and how should we proceed.
-=======reserved==========
and u sure this doesnt break recovery?
ok now that i read the post carefully i understand that it WILL BREAK recovery
DooMLoRD said:
and u sure this doesnt break recovery?
ok now that i read the post carefully i understand that it WILL BREAK recovery
Click to expand...
Click to collapse
cons highlighted to avoid confusion.
any idea how we can get this piece to work.
BTW why do we need it when we have app2sd ?
How's it better ?
anantshri said:
cons highlighted to avoid confusion.
any idea how we can get this piece to work.
Click to expand...
Click to collapse
keep only one FAT32 partition...
modify the recovery ramdisk to mount that partition to /sdcard
DooMLoRD said:
keep only one FAT32 partition...
modify the recovery ramdisk to mount that partition to /sdcard
Click to expand...
Click to collapse
that could be done
however there is one more issue which i found just now
SDCARD can't be mounted to PC till both partitions are umounted and that won't be done automatically so we need alternative for sdcard umounting also
something like a gscript code for umounting /data/sdext2 before attempting sdcard mount to pc
the new vold introduced in froyo causes this issue
Adolf1994 said:
the new vold introduced in froyo causes this issue
Click to expand...
Click to collapse
the default vold.fstab listing is
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
some stuff online suggests that i can specify a partition number manually.
however
Code:
dev_mount sdcard /mnt/sdcard [B]1[/B] /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
when i am trying this it barks out and not even mounts sdcard.
With the sdcard parted in 3 partitions, I tried to make the third partition recognized by my pc, and I tried an application named multimount sd or something like that and it worked for me. You can found it in the market. With it, the pc can recognize the third partition not the first. Maybe that will help in your project.
Sent from my X10i
i meant the vold binary/system, not the fstab config
Adolf1994 said:
i meant the vold binary/system, not the fstab config
Click to expand...
Click to collapse
can you point me to the correct code for this.
fat32 is first partition
ext2 is second partition
vold.fstab
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
this will mount fat32 partition
dev_mount ext2 /mnt/sdcard 1 or 2 /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
should mount ext2 for link2sd
the vold from 2.1 works well as you can see and if you'd have googled it, then you'd know there is a revised version of vold in 2.2+
How about instead bind mounting a folder on /system as /data/sdext2 did this for ages on 2.1 to get more space for apps without probs. Obviously /system has to be mounted rw which isn't a prob for me and at least on stock there's loads of free space there which is a shame to waste.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o bind /system/app2 /data/sdext2
Think the folders need to be created first.
patch for using link2sd
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
aZuZu said:
fat32 is first partition
ext2 is second partition
vold.fstab
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
this will mount fat32 partition
dev_mount ext2 /mnt/sdcard 1 or 2 /devices/platform/msm_sdcc.1/mmc_host/mmc0 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.4/mmc_host/mmc1
should mount ext2 for link2sd
Click to expand...
Click to collapse
I also assumed something like this however android seems to be needing a last partition as vfat and that vfat is mounted as sdcard or nothing is mounted.
shaunbu said:
How about instead bind mounting a folder on /system as /data/sdext2 did this for ages on 2.1 to get more space for apps without probs. Obviously /system has to be mounted rw which isn't a prob for me and at least on stock there's loads of free space there which is a shame to waste.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mount -o bind /system/app2 /data/sdext2
Think the folders need to be created first.
Click to expand...
Click to collapse
for you i recommand checking http://forum.xda-developers.com/showthread.php?t=1206149 and also system being rw all the time is not at all a good idea.
tkymgr said:
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
Click to expand...
Click to collapse
Thanks buddy will check it as soon as possible ...rightnow my sdcard is not mounting nomatter what setting i do thinking of flashing CM7 and will see how it goes from there.
Note : just checked the zip i think SE stock needed a relacement at vold. will just flash the vold and see if it works.
tkymgr said:
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
Click to expand...
Click to collapse
Thanks buddy. I can confirm the SE 2.3.3 sample zip worked. I flashed the zip, turned off my x10, partitioned the sd on my pc using fat32 & ext32, powered on and DID NOT get previous error of sd not recognized on startup. It mounted fat32 partition and link2sd recognized ext2 partition right away. Selected ext type, rebooted again and I've moved apps that I wanted to the sd card. Rebooted a couple more times and apps are still linked and running fine. Time will tell if any apps will have issues or any tweaks on this rom will be affected. Using WBs v3.9 custom GB and I'll report again later.
Again thank you to everyone's efforts and for not giving up on this old feature.
Edit: Forgot to mention I can still enter xrecovery manually and using the xperia reboot app.
tkymgr said:
Hi,
because link2sd rearranges install-recovery.sh
I made a patch for patch for using link2sd
for CM7-Z-MOD-002
for SE 2.3.3 sample
Z's work contributes to all.
Thanks for Z !!
Cheers,
tkymgr
Click to expand...
Click to collapse
confirmed working
Post updated with details......
Please, note, that everything you had previously added to install-recovery.sh, is now renamed into install-recovery.sh.ori. So, if you want it back, working, you need to rename/copy to install-recovery2.sh
I formatted SDCard in ext2. But the phone gives the message "No SDCard or not formatted."
In Android Terminal Emulator I run commands:
su
umount /mnt/sdcard
mount -t ext2 /dev/block/mmcblk1p1 /mnt/sdcard
but nothing happens.
When I created in /mnt folder a new folder sdcard1 and run mount -t ext2 /dev/block/mmcblk1p1 /mnt/sdcard1, my card is successfully mounted to /mnt/sdcard1
1) Why it is not mounted to /mnt/sdcard? How to do it? How I can mount ext2 instead of FAT32?
2) How to make mount SDCard to /mnt/sdcard at boot?
is there anyway to mount the real sdcard to /sdcard?
i tried to edit the vold.fstab, but it just bootloop on the animation.
http://forum.xda-developers.com/showpost.php?p=23347641&postcount=14
he is mounting to "/mnt/sdcard" while i used "/sdcard"
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host/mmc2
where should it be mount to or is it because of different phone?
sams-roots said:
is there anyway to mount the real sdcard to /sdcard?
i tried to edit the vold.fstab, but it just bootloop on the animation.
http://forum.xda-developers.com/showpost.php?p=23347641&postcount=14
he is mounting to "/mnt/sdcard" while i used "/sdcard"
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host/mmc2
where should it be mount to or is it because of different phone?
Click to expand...
Click to collapse
/sdcard is normally a symbolic link pointing to /storage/emulated/legacy
There's an internal "sdcard" that normally gets mounted onto /mnt/shell/legacy from /init.qcom.rc - that's symlinked to /storage/emulated/legacy in that same file. It also appears to start up a daemon that re-mounts the internal "sdcard".
What are you trying to do? Normally the external SDcard is mounted to /mnt/extSdCard, so you should just store data there rather than /sdcard.
(Or /mnt/sdcard, /mnt/shell/legacy, /storage/emulated/legacy, or any of the other things simlinked to the internal sdcard.)