• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Q] [q] how to write a recovery.fstab for cwm?

Search This thread
I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.

So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?

thanks!
 

globula_neagra

Senior Member
Jun 28, 2009
261
79
Birmingham
I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.

So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?

thanks!



why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
 
  • Like
Reactions: suhridkhan

globula_neagra

Senior Member
Jun 28, 2009
261
79
Birmingham
try this recovery
what i did, i used the recovery.fstab from this http://forum.xda-developers.com/showthread.php?t=1484753

i would like to try the recovery from the 4ext and see what mount points and how the filesystem is managed.
if you have one share`it with me.



the attached files is the cwm that i cooked, using the stock recovery and adding the fstab from the 5.8 cwm

you can flash it and see what results you have (if you get anny errors)
but don`t use the recovery to flash something till you don`t get the mount results to see if the mounting points are like this, if the mounting points are like this you should be ok to try and flash a rom.

# mount point fstype device

/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
/data ext4 /dev/block/mmcblk0p26 fstype2=ext3
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p25 fstype2=ext3


to find out the mounting points
adb shell
mount


and you should have a long output like this (This are not from a htc desire s ! )

C:\Android\android-sdk\platform-tools>adb shell
uid=0 [email protected]:/ # mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p12 on /system type ext4 (ro,relatime,user_xattr,barrier=1,dat
a=ordered)
/dev/block/mmcblk0p13 on /data type ext4 (rw,nosuid,nodev,relatime,user_xattr,ba
rrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p14 on /persist type ext4 (rw,nosuid,nodev,relatime,user_xattr
,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,b
arrier=1,data=ordered)
/dev/block/mmcblk0p17 on /content type ext4 (rw,nosuid,nodev,relatime,user_xattr
,barrier=1,data=ordered)
/dev/block/vold/179:97 on /mnt/external_sd type vfat (rw,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:20 on /mnt/sdcard type 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)
/dev/block/vold/179:20 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
exec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
uid=0 [email protected]:/ #
 

Attachments

  • recovery.rar
    4.8 MB · Views: 389
Thanks for your effort, but i can't test the recovery properly because there is a key missing to run an option. I can browse through the menu with volume +/- though, but can't enable the selected option.

I found an 4ext Recovery (version 1005.5.0), i attached it with the fstab i extracted from it
 

Attachments

  • recovery_fstab.zip
    333 bytes · Views: 1,023
  • recovery.zip
    5.9 MB · Views: 258

globula_neagra

Senior Member
Jun 28, 2009
261
79
Birmingham
well, i could use the maping key from the cwm 5.8
there are some cwm`s that need enabling
for example on a tablet i need to press 27 times the volume key -, or a combination of + - + (volume keys) to enable the selection.

i can not test the recovery, i will rebuild later on a version based on the 5.8 key maping.
on the screen did you got any errors ?
 
  • Like
Reactions: Adromir
Havent tried the keys on my Build, but with yours they are working.

In the cwm i got this errors:

I:Skipping execution of extended command, file not found
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc

Now trying to make a Backup, that seems to work, but i am not completly sure, havent tried to restore it yet. Will do that tomorrow
 

globula_neagra

Senior Member
Jun 28, 2009
261
79
Birmingham
this is the first cwm that i made for you, but with the key maping from the stock recovery
http://www.mediafire.com/?kc8dk9gl2c9660o

---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------

you can check the recovery files on the sd card, if you see there the boot.img recovery, and system/data mds5 it should be ok to restore.
 

globula_neagra

Senior Member
Jun 28, 2009
261
79
Birmingham
yes it is different, it is like the first build but i used the key mapping from the htc desire s stock recovery, the one from the ruu

well the tips are, keep trying till you get something working.

for example on my tablet i am using a htc sensation xl recovery (not all the stuff only the recovery which is in the sbin directory if you unpack the recovery)


unpack the stock recovery, and analyse the recovery.fstab by comparing it to the mount points, if they are ok is very good, you will have bigger chance to get something working.
try and use the clockwork builder and see if you get any results, but select the stock recovery.fstab (you have the option when you cook the recovery, is the second option)
if you don`t get any results like this try to find a similar device from a spec point of view and steal the /sbin/recovery from the device cwm recovery, put it on your recovery, repack and test.

it depends on what tablet you have also :)

If you need help in the future, send me a pm, because i check only once per week this section of the forum.
 
  • Like
Reactions: Adromir
Ok, found boot.img but no system/data and system.ext3.dup is only about 100kb of size. Is that correct?

in the logfile there are three errors:

W:Unable to get recovery.fstab info for /datadata during fstab generation
W:Unable to get recovery.fstab info for /emmc during fstab generation
W:Unable to get recovery.fstab info for /sd-ext during fstab generation
 

globula_neagra

Senior Member
Jun 28, 2009
261
79
Birmingham
no, is not corect, that means that the recovery made by the clockworok server has some flaws
i will try to make a new one, based on 4ext recovery

---------- Post added at 07:47 PM ---------- Previous post was at 07:31 PM ----------

K, i remade the fstab

it looks like this now


# mount point fstype device

/recovery emmc /dev/block/mmcblk0p21
/boot emmc /dev/block/mmcblk0p22
/cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
/data ext4 /dev/block/mmcblk0p26 fstype2=ext3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p25 fstype2=ext3
/sd-ext ext4 /dev/block/mmcblk1p2 fstype2=ext4
/system_lib ext4 /dev/block/mmcblk0p28 fstype2=ext4



You could try and find a similar device that has the version 6 recovery and try the recovery from that device (am talking about getting the recovery, unpack it, take the recovery file which is in boot.img-ramdisk\sbin\recovery


In the end, it`s all about testing :)
I did all my stuff alone, nobody helped me.
http://www.mediafire.com/?69a74qq9idko02v this is the recovery based on the recovery.fstab from the 4ext recovery which looks more complete.
 

andriboy923

Member
Jan 21, 2013
8
3
Bandung
Help me plz..

I don't haved knowledge about android scripting or any something like that,.. but I was try hard to get and learn about creating CWM of my stock recovery.img .. after all is unfortunately .. always failed.
I haved try on builder.clockworkmod.com but itsn't success,...

would any member in here should help me to create CWM from my stock recovery.img please... my phone is One Scribe ZA987 with MTK6577
 

Attachments

  • recovery.img
    6 MB · Views: 35

dazza9075

Senior Member
Jul 22, 2007
2,854
490
Glasgow
Hi Guys, I have a quick question

I am new to this but im learning quickly.... I think!

im making up my own recovery and so far my recovery.fstab looks like this:

/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/cache ext4 /dev/block/mmcblk0p10 fstype2=ext3
/data ext4 /dev/block/mmcblk0p12 fstype2=ext3
/system ext4 /dev/block/mmcblk0p11 fstype2=ext3
/factory ext4 /dev/block/mmcblk0p4 fstype2=ext3
/crypo emmc /dev/block/mmcblk0p3

but when trying to do a backup it throws up an error saying it cant write to SDCARD, which makes sense as its not mounted

So, the question is, how do I go about mounting it for recovery?

Now, the sdcard is internal, there is no external card, I believe its symlinked to /storage/sdcard within android which is all located in the partition /data/ (mmcblk0p12)

sooo, can anyone help, ive been trawling the interweb and I can find lots of ways to do this within the main OS, but how do I go about it for recovery.fstab to be used in a custom clockwork recovery img
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    try this recovery
    what i did, i used the recovery.fstab from this http://forum.xda-developers.com/showthread.php?t=1484753

    i would like to try the recovery from the 4ext and see what mount points and how the filesystem is managed.
    if you have one share`it with me.



    the attached files is the cwm that i cooked, using the stock recovery and adding the fstab from the 5.8 cwm

    you can flash it and see what results you have (if you get anny errors)
    but don`t use the recovery to flash something till you don`t get the mount results to see if the mounting points are like this, if the mounting points are like this you should be ok to try and flash a rom.

    # mount point fstype device

    /recovery emmc /dev/block/mmcblk0p21
    /boot emmc /dev/block/mmcblk0p22
    /cache ext4 /dev/block/mmcblk0p27 fstype2=ext3
    /data ext4 /dev/block/mmcblk0p26 fstype2=ext3
    /sdcard vfat /dev/block/mmcblk1p1
    /system ext4 /dev/block/mmcblk0p25 fstype2=ext3


    to find out the mounting points
    adb shell
    mount


    and you should have a long output like this (This are not from a htc desire s ! )

    C:\Android\android-sdk\platform-tools>adb shell
    uid=0 [email protected]:/ # mount
    mount
    rootfs on / type rootfs (ro,relatime)
    tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
    devpts on /dev/pts type devpts (rw,relatime,mode=600)
    proc on /proc type proc (rw,relatime)
    sysfs on /sys type sysfs (rw,relatime)
    none on /acct type cgroup (rw,relatime,cpuacct)
    tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
    tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
    none on /dev/cpuctl type cgroup (rw,relatime,cpu)
    /dev/block/mmcblk0p12 on /system type ext4 (ro,relatime,user_xattr,barrier=1,dat
    a=ordered)
    /dev/block/mmcblk0p13 on /data type ext4 (rw,nosuid,nodev,relatime,user_xattr,ba
    rrier=1,data=ordered,noauto_da_alloc)
    /dev/block/mmcblk0p14 on /persist type ext4 (rw,nosuid,nodev,relatime,user_xattr
    ,barrier=1,data=ordered)
    /dev/block/mmcblk0p15 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,b
    arrier=1,data=ordered)
    /dev/block/mmcblk0p17 on /content type ext4 (rw,nosuid,nodev,relatime,user_xattr
    ,barrier=1,data=ordered)
    /dev/block/vold/179:97 on /mnt/external_sd type vfat (rw,dirsync,nosuid,nodev,no
    exec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
    cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
    /dev/block/vold/179:20 on /mnt/sdcard type 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)
    /dev/block/vold/179:20 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,no
    exec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=
    cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
    tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
    uid=0 [email protected]:/ #
    1
    I am trying to port cwm 6.0.1.4 for my HTC Desire S via the cwm builder. Its running so far, but not exactly working, because it doesnt mount all partitions correctly. So i assume, there must be something wrong with my recovery.fstab. I used an older recovery.fstab i found on the internet, but maybe it hasnt got the right "options" to mount all partitions correctly.

    So can anybody explain me, how to make a working one? Which partitions are needed and how they have to be mounted?

    thanks!



    why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
    1
    well, i could use the maping key from the cwm 5.8
    there are some cwm`s that need enabling
    for example on a tablet i need to press 27 times the volume key -, or a combination of + - + (volume keys) to enable the selection.

    i can not test the recovery, i will rebuild later on a version based on the 5.8 key maping.
    on the screen did you got any errors ?
    1
    here is the touch one, check also if the key`s are working

    the recovery that you made, the keys where working ?
    1
    yes it is different, it is like the first build but i used the key mapping from the htc desire s stock recovery, the one from the ruu

    well the tips are, keep trying till you get something working.

    for example on my tablet i am using a htc sensation xl recovery (not all the stuff only the recovery which is in the sbin directory if you unpack the recovery)


    unpack the stock recovery, and analyse the recovery.fstab by comparing it to the mount points, if they are ok is very good, you will have bigger chance to get something working.
    try and use the clockwork builder and see if you get any results, but select the stock recovery.fstab (you have the option when you cook the recovery, is the second option)
    if you don`t get any results like this try to find a similar device from a spec point of view and steal the /sbin/recovery from the device cwm recovery, put it on your recovery, repack and test.

    it depends on what tablet you have also :)

    If you need help in the future, send me a pm, because i check only once per week this section of the forum.