I have not seen these mount points posted anywhere for handy reference...
These are mount points for CWM and ADB
•mmcblk0p1 - Boot (vfat)
•mmcblk0p2 - Rom
•mmcblk0p3 - Device specific files (serial number, etc) and Factory.zip (flashable zip that returns NC to factory settings)
•mmcblk0p4 - Logical Partition (Nothing of use here)
•mmcblk0p5 - System
•mmcblk0p6 - Data
•mmcblk0p7 - Cache (vfat)
•mmcblk0p8 - Media (vfat)
These are mount points for Nooter .2
•mmcblk0p1 - SDCARD
•mmcblk1p1 - Boot (vfat)
•mmcblk1p2 - Rom
•mmcblk1p3 - Device specific files (serial number, etc) and Factory.zip (flashable zip that returns NC to factory settings)
•mmcblk1p4 - Logical Partition (Nothing of use here)
•mmcblk1p5 - System
•mmcblk1p6 - Data
•mmcblk1p7 - Cache (vfat)
•mmcblk1p8 - Media (vfat)
Lol, I thought this thread said "moot" points
modembug said:
I have not seen these mount points posted anywhere for handy reference...
Click to expand...
Click to collapse
Besides here, you mean?
Your info is wrong. mmcblk0 is the emmc. mmcblk1 is the sdcard.
Also, the stock file system types are ext2 for system, ext3 for data. Gingerbread uses ext4 for both.
dangit i suck! I looked on nook devs last night for that list and didnt find it!
I have updated the mount points to reflect both nooter and adb/cwm...
fattire said:
Besides here, you mean?
Your info is wrong. mmcblk0 is the emmc. mmcblk1 is the sdcard.
Also, the stock file system types are ext2 for system, ext3 for data. Gingerbread uses ext4 for both.
Click to expand...
Click to collapse
In the guide modembug linked on AndroidCentral (see here: http://forum.androidcentral.com/bar...how-install-nookie-froyo-internal-memory.html), it says to do this:
Code:
mount -o remount,rw /dev/block/mmcblk1 /
mkdir tmpfolder
mount /dev/block/mmcblk0p5 tmpfolder
cd tmpfolder
rm -r *
cd ..
mount /dev/block/mmcblk0p6 tmpfolder
cd tmpfolder
rm -r *
cd ..
umount tmpfolder
rmdir tmpfolder
Why is this necessary? Specifically, why the remount to rw of /, when you could just create a directory in /data for this purpose?
Also, why is it apparently not necessary to delete the contents of /boot (mmcblk0p1) but it is for /system and /data?
starkruzr said:
In the guide modembug linked on AndroidCentral (see here: http://forum.androidcentral.com/bar...how-install-nookie-froyo-internal-memory.html), it says to do this:
Code:
mount -o remount,rw /dev/block/mmcblk1 /
mkdir tmpfolder
mount /dev/block/mmcblk0p5 tmpfolder
cd tmpfolder
rm -r *
cd ..
mount /dev/block/mmcblk0p6 tmpfolder
cd tmpfolder
rm -r *
cd ..
umount tmpfolder
rmdir tmpfolder
Why is this necessary? Specifically, why the remount to rw of /, when you could just create a directory in /data for this purpose?
Also, why is it apparently not necessary to delete the contents of /boot (mmcblk0p1) but it is for /system and /data?
Click to expand...
Click to collapse
Boot gets overwritten data and system leave remnants i.e. dalvik cache which causes boot issues
Sent from my PC36100 using XDA App
Related
This is cwm for your xperia u with locked bootloader, but this is beta version
FILES FOR XPERIA U
recovery.fstab
Code:
# mount point fstype device [device2] fstype2
/cache ext4 /dev/block/mmcblk0p12
/data ext4 /dev/block/mmcblk0p11
/system ext4 /dev/block/mmcblk0p10
/sdcard vfat /dev/block/mmcblk0p14
/boot emmc /dev/block/mmcblk0p9
fstab
Code:
/cache ext4 /dev/block/mmcblk0p12
/data ext4 /dev/block/mmcblk0p11
/system ext4 /dev/block/mmcblk0p10
/sdcard vfat /dev/block/mmcblk0p14
/boot emmc /dev/block/mmcblk0p9
bootrec
Code:
#!/sbin/sh
# trigger button-backlight
echo '255' > /sys/class/leds/r-key-blue/brightness
echo '255' > /sys/class/leds/m-key-red/brightness
echo '255' > /sys/class/leds/l-key-green/brightness
cat /dev/input/event2 > /dev/keycheck&
sleep 3
# trigger button-backlight
echo '0' > /sys/class/leds/r-key-red/brightness
echo '0' > /sys/class/leds/l-key-red/brightness
echo '0' > /sys/class/leds/m-key-red/brightness
kill -9 $!
fi
if [ -s /dev/keycheck -o -e /cache/recovery/enterrecovery ]
then
rm /cache/recovery/enterrecovery
mount -o remount,rw rootfs /
# shifting to "umount -l /partition" to avoid mounting issues in recovery
stop cspsa
stop tad
killall -9 cspsa-server
killall -9 logwrapper
killall -9 chargemon
killall -9 tad
umount -l /system
umount -l /data
umount -l /cache
umount -l /sdcard
umount -l /mnt/sdcard
rm -r /sdcard
rm -r /not/sdcard
mkdir /sdcard
mkdir /tmp
rm /etc
mkdir /etc
cp /recovery.fstab /etc/recovery.fstab
mount /dev/block/mmcblk0p14 /sdcard
/sbin/recovery &
/sbin/ps >/sdcard/ps.log
# DooMLoRD - enable USB Mass Storage mode - thanks to Napstar
echo 1 > /sys/devices/virtual/usb_composite/usb_mass_storage/enable
/sbin/recovery &
/sbin/adbd_rec recovery
fi
IM INTEGRATE THIS IN MY AOKP
works
everythings
mount /data
mount /cache
mount /sdcard
mount /usb
CHANGELOG:
BETA 1
FIXED MOUNT DATA AND USB
BETA 2
THE BAR LIGHTS IS ON IN RECOVERY MOD NICE!!!
FOR NOW THIS HAVE SOME BUGS
BETA 3
FIXED SOME ISSEUES
BUGS: ONLY MOUNT SYSTEM
BETA 4
NEW AOKP LOGO
NOW YOU CAN FORMAT /SYSTEM....BUT NOT FLASH ROMS
BETA 5
FIXED MOUNT /SYSTEM (From bootrec from Atis112)
FIXED Bootrec
Fixed Bootrec-Device
Fixed Bootrec-devce-fs
ITS MY CWM... NOT CWM MODIFY FROM ATIS112
IM ADD SOME FEATURES TO THISS CWM
INSTALLATION
RENAME TO recovery.tar AND PUT IN SYSTEM/BIN AND CHANGE PERMISSIONS
DOWNLOAD: HERE
maybe you need to check if the recovery is gaining access to root, check the mountpoint, etc...
xperiafan13 said:
This is cwm for your xperia u with locked bootloader, but this is beta version
bugs:
Cant mount system
I NEED TO FIX MOUNT SYSTEM... PLEASE HEELP ME!!!!
IM INTEGRATE THIS IN MY AOKP
works
everythings
mount /data
mount /cache
mount /sdcard
mount /usb
Click to expand...
Click to collapse
Wait my next rom.
Sent from my Xperia U using xda premium
THANKS
atis112 said:
Wait my next rom.
Sent from my Xperia U using xda premium
Click to expand...
Click to collapse
BUT IM MAKE MI CUSTOM RAMDIZK AND RECOVERYS FOR MY ROM,I'm about going on holiday, and now if I can give more time to ANDROID
New beta aviable
This is in progress, not flly working, is oly for development.....
The light bar is on in recovery
Delete.
HELLO
This is my personnel recovery, this is not a copy of CWM of Atis112, eh I repaired the system assembly from its bootrec, keeping the light bar is always turned on, I will initiate my own projects, this is different from CWM of Atis112, thank him for the fix, likewise warn my AOKP version will have a new morning, I no longer have tested and reboots ...
some new things will
Enabled 2D acceleration
LED repaired
Greater stability guaranteed
No more delays on lockscreen
Posted AndyX modules, activatable Romcontrol
All applications updated
Based on FXP 148
AND MORE
What are the main diferences between your cwm and attis ?
Hi to all. I'm Abe Wayer.
I'm dreaming to start changing at first my own mobile OS end maybe going to develop a day.
Today it's just all the afternoon that i google....
I became root, I partitioned my sd and installing sdk & adb tools in a couple of days.
something goes quickly something not.
I have a galaxy ace with 2.3.6
I thought to start my develop time using adb.
first at all adb push.
So i made:
adb push test.txt /sdcard/test.txt
And i have: permission denied
I googled a lot and nothing worked:
Debug usb is on.
I umounted sdcard from /media (I use linux)
I've tried this as well:
mount -o remount , rw /dev/block/void/179:9 /sdcard
or
mount -r -w -o remount -t vfat /dev/block/void/179:9 /sdcard
But nothing work!
If im not able to push a file on a sd what i dream for?
My sdcard has two partition linux call them sdc1 & sdc2 first is 1500 Mib second 400
Thanks for your help
No Links too?
Please give me a hand!:crying:
Dont you have a guide ive not fought?
Please.....
News:
I've tried:
adb shel => su =>fdisk -l
and i've got the device name but if do:
# mount rw -o remount, rw -t fat32 /dev/stl10 /sdcard
I always have:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
But is there somewhere on the web an adb shel man complete with examples?
How do i obtain -w permission on my sd card?
adb pull works so i can read....
if i try ls -l /sdcard i got: lrwxrwxrwx root root 2012-12-18 02:01 sdcard -> /mnt/sdcard
So root can write.
Have i to change owner to the card?
Or simply with adb i'd say i'm root?
have i to umount sdcard?
Please!
Abe Wayer said:
# mount rw -o remount, rw -t fat32 /dev/stl10 /sdcard
Click to expand...
Click to collapse
Wrong usage, correct usage (provided that the device is correct):
Code:
mount -o rw, remount -t fat32 /dev/stl10 /sdcard
RoberGalarga said:
Wrong usage, correct usage (provided that the device is correct):
Code:
mount -o rw, remount -t fat32 /dev/stl10 /sdcard
Click to expand...
Click to collapse
Doesn't work as well.
my fdisk -l output is this:
# fdisk -l
Disk /dev/bml10: 41 MB, 41943040 bytes
255 heads, 63 sectors/track, 5 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/bml10 doesn't contain a valid partition table
Disk /dev/stl10: 37 MB, 37748736 bytes
255 heads, 63 sectors/track, 4 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Abe Wayer said:
if i try ls -l /sdcard i got: lrwxrwxrwx root root 2012-12-18 02:01 sdcard -> /mnt/sdcard
So root can write.
Click to expand...
Click to collapse
You don't know that. This is just a symbolic link, not the volume itself. Do:
$ ls -l /mnt/sdcard
This will show you if the card is mounted properly. Also issue a "mount" command, no parameter. But you should not need to remount it, the sdcard is handled by magic via the vold daemon. As soon as you remove it from the GNU/Linux machine, vold will mount it in Android.
kuisma said:
Y
Do: $ ls -l /mnt/sdcard
.
Click to expand...
Click to collapse
With ls - /mnt I have:
# ls -l /mnt/
drwxr-xr-x root system 2012-12-18 02:01 obb
drwxr-xr-x root system 2012-12-19 14:27 asec
drwx------ root root 2012-12-18 02:01 secure
d--------- system system 2012-12-18 02:01 sdcard
So sdcar has not permissions?
mount about sdcard says
/dev/block/vold/179:9 /mnt/sdcard 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,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec 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,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
It goes to be mounted rw but for some errors it came to be remounted ro?
I've proved with:
mount -o rw, remount -t vfat /dev/block/vold/179:9 /sdcard , And
mount -o rw, remount -t vfat /dev/block/vold/179:9 /mnt/sdcard
but the answer's always:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
any ideas?
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
Your sdcard is mounted just fine, no need to try to change anything there. Don't confuse the sdcard with its mount point, different things.
Make sure you've got read access to your test file, and push it to some place you know you are allowed to write. And use the full path /mnt/sdcard/file.name just to be sure.
Also, again, do a "ls - l /mnt/sdcard" to see its really there.
I had the same problem when I didn't root correctly, check if you have root correctly by using a root app. (like root checker or root explorer)
Hi,
As the title says, Is there Kernel loop support for our LG Optimus L9 ?
I'm trying to mount a loop file created on debian on the device, but I get the error
ioctl LOOP_SET_FD failed: Device or resource busy
Click to expand...
Click to collapse
.
This is what I did --
Loop file created on debian and formatted with ext4.
On Optimus L9 with CM10.1, in terminal emulator,
$su
#losetup /dev/block/loop0 /storage/sdcar1/file
#mount -o remount,rw /system
#mkdir /system/temp
#mount -rw -o loop -t ext4 /dev/block/loop0 /system/temp/
ioctl LOOP_SET_FD failed: Device or resource busy
#
Click to expand...
Click to collapse
Is our kernel having loop support. If yes, am I doing anything wrong? The file gets successfully mounted in Debian.
EDIT:
using "busybox mount" solved the issue.
Tried adding busybox to the mount command and voila it worked.
#busybox mount -rw -o loop -t ext4 /dev/block/loop0 /system/temp/
Click to expand...
Click to collapse
You just taught me something new, thanks.
Can you upload your img, I would really like to check this out, or can you direct me to a thread so I can learn some more.
Sent from my LGMS769 using xda app-developers app
kuma82 said:
You just taught me something new, thanks.
Can you upload your img, I would really like to check this out, or can you direct me to a thread so I can learn some more.
Sent from my LGMS769 using xda app-developers app
Click to expand...
Click to collapse
The one I created is over 100MB. I had a html tutorial containing 12,000 files. I don't want to put those files on sdcard and mess it up. So, I used this block device.
I have created a sample "temp.img" file with a size of 500KB. It contains a single text file. I'm attaching it and you can check it out.
Below is the way i created and mounted it.
Code:
# "temp.img" md5 b97642fed817fa3f1a0cc6dc64b6c40d
# remount rootfs rw.
mount -o remount,rw /
# create mount point.
mkdir /mnt/temp
# chmod mountpoint.
chmod 777 /mnt/temp
# create block file.
dd if=/dev/zero of=/storage/sdcard0/temp.img bs=1024 count=500
# this creates 500 KB file. I can't seem
# to get bs=1M argument working on android.
# so bs1024 x count = target file size (=count times in KB).
# query free loop device. (will be /dev/block/loopx)
losetup -f
#attach block file with free loop.
losetup /dev/block/loop0 /storage/sdcard0/temp.img
#create file system.
mke2fs -T ext2 /dev/block/loop0
# And finally mount it
busybox mount -o loop -t ext2 -rw /dev/block/loop0 /mnt/temp
# For unmounting
busybox umount /mnt/temp
And it isn't encrypted. I don't need encryption, and i can't even seem to figure out how to encrypt it.
I have a second partition on my SDCARD at /dev/block/mmcblk1p2, all I want to do is ensure that it is always mounted as /storage/sdcard0/mount seems simple I can do it in 5 second on Linux, on Android, it seems impossible I can try to add a hack, but that is lost every-time I update the ROM. There has to be some simple way to do it, that I'm missing. The best I have is to load up a terminal emulated su to root and run: mount -t ext4 /dev/block/mmcblk1p2 /storage/sdcard0/mount
Now in theory, the following would work but for 2 things:
mkdir /storage/sdcard0/mount
su - root -c 'mount -t ext4 /dev/block/mmcblk1p2 /storage/sdcard0/mount'
But for the fact the Android's su does not understand -c so that is out. as well as the fact that non-root users (u0_a216 in my case) can not access /storage/sdcard0.
All I want is a simple way to ensure that this is always mounted where I want it when I need it, yet this simple task is nearly impossible it appears on Android, so why is that?
The issue here is that the fat32 partition does not support large files so I need a separate partition that does such as ext4, in reality if the external sdcard could just be ext4 there would be no issues, and it would be faster, but that is Android for you.
Any suggestions?
Thanks,
ERIC
Insert mount script to init.d folder...
via XDA Premium
Ok, I have this mostly working with juicessh and tasker now for now
I have 2 shell scripts:
mountDev.sh:
Code:
mkdir /storage/sdcard2
chmod 777 /storage/sdcard2
mount -t ext4 /dev/block/mmcblk1p2 /storage/sdcard2
umountDev.sh
Code:
umount /storage/sdcard2
rmdir /storage/sdcard2
In Tasker I have 2 tasks defined:
I'm using the JuiceSSH plugin to open a terminal to localhost I then execute:
To Mount:
Code:
su -l --shell=/system/bin/sh --command='cd /storage/sdcard0 ; sh ./mountDSev.sh ; exit' ; exit
To umount:
Code:
su -l --shell=/system/bin/sh --command='cd /storage/sdcard0 ; sh ./mountDSev.sh ; exit' ; exit
I then created 2 icons, 1 for each operation on the home screen. I also created a Device Boot event to automatically execute and mount the task.
This works, mostly, however even though it is root, sometimes I get errors such as /storage/ is readonly, which makes no sense since it could create the directory at boot, but can not remove the directory later on, since it is readonly. Its a minor thing currently, but annoying.
The benefit of this is it is easy to transfer between ROM images and devices without worrying about it being wiped out every-time I update. In theory it also works without init.d support being enabled. Down side is it you need Tasker and the JuiceSSH plug-in so it costs money.
Hope this helps others.
ERIC
What I want to do is partition my sdcard into 2 parts, 1 fat32 and the second as ext3. Mount both partitions at startup so i get /sdcard (fat) and /sdcardext3 (ext). Then create 2 folders /sdcardext3/apps and /sdcardext3/apps-private then delete the /data/apps and /data/apps-private folders and replace them with links to the folders on the sdcard 2nd partition I just created. Is this possible? I guess I'll be having to muss around with fstab but I'm not too well versed on that. Anyone got any tips on how I can achieve this. I know there are apps like foldermount and link2sd but they only work on a per app basis, i want a full "do it and forget it" solution that doesn't rely on an app.
Cheers
EDIT:
I'm seeing these 3 lines in /init.rc
Code:
mount rfs /dev/stl11 /data nosuid nodev usedm check=no
chown system system /data
chmod 0771 /data
Is it possible to create and format an rtf partition on the sdcard, then extract, change and repack the ramdisk image with the following changes?
Code:
mount rfs /dev/block/vold/179:2 /data nosuid nodev usedm check=no
chown system system /data
chmod 0771 /data
To move the data folder completely off the phone internal memory. My phone only has 512MB and my external SD is 64GB so I won't cry at the wasted half a gig.
So far I've managed to:
extract the boot.img from the stock firmware I'm using. Using a linux box with abootimg installed (apt-get abootimg)
I split it up into the kernel (zImage) and the ramdisk (initrd.img) .
Unpacked and cpio-ed initrd.img to files.
Edited init.rc and found two instances of
Code:
mount rfs /dev/stl11 /data nosuid nodev usedm check=no
in the file
Replaced /dev/stl11 with /dev/block/mmcblk0p2 and replaced rfs with ext3.
Combined the kernel and ramdisk back together with gzip, cpio and abootimg (newboot.img) and dumped it onto the phone using adb along with the flash_image command (which wasn't on the phone as standard).
Had to copy flash_image (in fact I had to cat flash_image >/data/flash_image because there's no cp command as standard either) to /data as it needed executable privs, chmod 777 /data/flash_image to allow it to execute,
Then execute /data/flash_image boot /sdcard/newboot.img
Reboot phone
Phone;s stuck on the Samsung splash screen, pah. Was worth a try anyway.