[Q] Need help with mount points - Android Q&A, Help & Troubleshooting

[Q] Need help with mount points - Android Q&A, Help & Troubleshooting

Hey guys, I was recently given a Galaxy Tab 3 Lite (SM-T110) and have found very little roms considering its an old tablet and none are with my latest stock firmware. That said, I'm trying to implement this tablet into dsixda's kitchen but am having a little bit of trouble.
I have set up the kitchen successfully on Windows 10 using cygwin and have even complied a rom successfully but the problem is when I flash it it gives me errors about boot.img mounting points. I pretty much have 3 questions:
1. Cant find my boot mnt point and was wondering if someone can help me find it? (ill attach my recovery.fstab file in the bottom for you to see)
2. Dont really know if I need that "fix_boot2=yes" line? "fix_boot=yes" line? Or none? How can I tell if i need it?
3. Since boot mount point is not inside recovery.fstab file, does that mean it is not need to be mentioned?
I made a file called "goyawifi" inside the edify_defs folder with the following info inside it:
# Samsung Galaxy Tab 3 Lite SM-T110
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p15
cache_mnt=\/dev\/block\/mmcblk0p14
boot_mnt=\/dev\/block\/mmcblk0p15
data_mnt=\/dev\/block\/mmcblk0p16
sdcard_mnt=\/dev\/block\/mmcblk1p1
fix_boot2=yes
And this is my recovery.fstab info:
#mount point fstype device [device2]
/mrd emmc /dev/block/mmcblk0p1
/mrd1 emmc /dev/block/mmcblk0p2
/mep2 emmc /dev/block/mmcblk0p3
/efs ext4 /dev/block/mmcblk0p4
/dtim emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p9
/kernel emmc /dev/block/mmcblk0p10
/radio emmc /dev/block/mmcblk0p11
/custom ext4 /dev/block/mmcblk0p12
/preload ext4 /dev/block/mmcblk0p13
/cache ext4 /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p16 length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/mnt/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Can anyone please help me to start customizing/flashing my rom? Thanks in advance...
FWI: When I say "successfully compiled a rom" I mean that the kitchen makes a rom, but upon flashing it, it gives me an error. Something about boot.img not mounted right

Bump! 45 views and no replies? So many developers here, surely someone knows the answer to my problems

Tried again to build a rom using dsixda's Android Kitchen, would like to find boot mount points... can anybody help?

Sorry, I don't have this device to test, but I think you should check "/kernel emmc /dev/block/mmcblk0p10"
Here should be the kernel image and maybe not the whole boot.img !
As you already know , boot.img have a kernel image and a ramdisk .... but on your device , ramdisk may be under /system ... I'm not 100% sure ... but from what you've posted so it seems !
So, there is no partition on your device for boot.img ... anyway you can make a custom rom also in this case, but you should know how to flash the new kernel image and also the ramdisk !
Unfortunately Samsung has made this device quite difficult for development, but not impossible .
Good luck !

Related

HELP Porting Recovery for Droppad A8HD

I'm trying to port CWM for my device.
I need to replace iunin with CWM.
The problem is that I cannot extract the recovery img. I have a recovery.img but cannot edit/mount it (tried as ext2/3/4, gzip and so on).
Recovery is flashed as fastboot flash recovery.img (what type of image is this .img file??).
Here are is the recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p2
/cache ext3 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p3
/kernel mtd kernel
/ramdisk mtd ramdisk
/misc mtd misc
/boot mtd boot
/recovery mtd recovery
/bootloader mtd bootloader
/radio mtd radio
I have read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images and similar posts but they don't work for me (no Android magic...).
Please point me in the right direction, how to mount this recovery.img file - that's all I need.
Thank you!

mexusbg said:
I'm trying to port CWM for my device.
I need to replace iunin with CWM.
The problem is that I cannot extract the recovery img. I have a recovery.img but cannot edit/mount it (tried as ext2/3/4, gzip and so on).
Recovery is flashed as fastboot flash recovery.img (what type of image is this .img file??).
Here are is the recovery fstab:
Code:
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1
/system ext4 /dev/block/mmcblk0p2
/cache ext3 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p3
/kernel mtd kernel
/ramdisk mtd ramdisk
/misc mtd misc
/boot mtd boot
/recovery mtd recovery
/bootloader mtd bootloader
/radio mtd radio
I have read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images and similar posts but they don't work for me (no Android magic...).
Please point me in the right direction, how to mount this recovery.img file - that's all I need.
Thank you!
Click to expand...
Click to collapse
Just to clarify you are trying to mount the recovery.img on your PC?

thewadegeek said:
Just to clarify you are trying to mount the recovery.img on your PC?
Click to expand...
Click to collapse
Yeah I'm trying to mount the recovery.img and replace iunin recovery files with cwm's files.
I tried:
gunzip -c ../your-ramdisk-file | cpio -i
gzip: recovery.img: not in gzip format
cpio: premature end of archive
./split_bootimg.pl recovery.img
Android Magic not found in recovery.img. Giving up.
Also I don't have /dev/mtd/ ....
I've attached the recovery.img file if someone want's to check it out.
EDIT: I tired dsixda-Android-Kitchen and still cannot mount/unpack recovery.img.
EDIT2: List of other files in the update.zip:
zImage-GB-v746-2703 - KERNEL
system-GB-1.3-2703.ext4 (EXT4 image) - System
ramdisk-uboot-GB-1.3-2703.img - ramdisk
ramdisk-recovery-uboot-GB-1.0.img - recovery
Link to the whole firmware: https://dl.dropbox.com/u/41124284/A8HD/Firmware/um2703-GB-1.3-sdUp-381.zip
Please help me.

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

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!

Adromir said:
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!
Click to expand...
Click to collapse
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?

globula_neagra said:
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
Click to expand...
Click to collapse
Because with just the stock Recovery it doesn't mount all needed partitions correctly. I took the stock recovery i extracted from the latest RUU.

give me the stock recovery and i will do the recovery.fstab for you

globula_neagra said:
give me the stock recovery and i will do the recovery.fstab for you
Click to expand...
Click to collapse
Here it is. Thats really great! Thanks a lot

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]:/ #

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

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 ?

No, it didnt show any errors yet. Is it possible to make it touch too? I tried to cook up a cwm with the fstab of 4ext but it completly failed to load any partition. 4ext itself is working though

here is the touch one, check also if the key`s are working
the recovery that you made, the keys where working ?

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

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.

Is this different from the built you attached last? This works fine with the keys.
btw. can you maybe give me some tips how you built it? Later i want to make a new cwm for my tablet, but i dont want to bother you with that too

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.

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

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.

Thanks very, very much, i really appreciate your efforts. So now, i'll start trying and trying until i get a working one

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

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

globula_neagra said:
why dont you dump the recovery from your phone, unpack and use the recovery.fstab from the stock recovery ?
Click to expand...
Click to collapse
can you explain to me how to dump? my phone is brigadier

how to Add New HTC Device to Android Kitchen

I already get the recovery.fstab as following
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 cache
/data ext4 userdata
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 system
/devlog ext4 devlog
/internal_sdcard vfat /dev/block/mmcblk0p35
to add new device create file in edify_defs with the same of device, as above listed mount point how can I edit the new file
Thanks for help

[Q] help with recovery.fstab

Could someone please help me with this recovery.fstab file for the hisense sero 7 lt tablet? It looks like the partitioning is messed up but im not completely sure. Im trying to make a partition file for android kitchen and thats why i need help with this recovery.fstab.
i cant attach the recovery.fstab so i'll copy and paste whats in it
recovery.fstab
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/boot mtd boot
/cache ext4 /dev/block/mtd/by-name/cache
/data ext4 /dev/block/mtd/by-name/userdata
/kernel mtd kernel
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mtd/by-name/user lun=/sys/class/android_usb/android0/f_mass_storage/lun/file
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 lun=/sys/class/android_usb/android0/f_mass_storage/lun1/file
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/mtd/by-name/system
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thank you for helping me!!

Well, I'm also in the progress of trying to figure this out, but try this:
get an ADB shell, or use a terminal app from the Play Store,
and execute:
Code:
cat /proc/mtd
That should give a list of partitions and their dev codes.
Tip: when posting files or code, try to make use of the code tags,
text inside them will be displayed with a monospaced font, so things will be more readable.
See more info here.

Thanks for the tip and I figured it out by using
cat /proc/partitions and cat /proc/mtd
Click to expand...
Click to collapse
those commands gave me the names of the partitions and what block number they are. Credit goes to Abdul_pt for giving me the partitions command credit goes to you hamc0re for helping me with the mtd command
Sent from my Amazon Otter2 using Tapatalk

[Q] Need Assist in defining new device in dsixda's kitchen

Hello, my device is not defined in dsixda's kitchen. And i could not define my device on my own in kitchen. I need some help in defining my device. Please , help me. i will provide with all the information required about my device please build it for me..

Here are the information i get when i open recovery.fstab
# mount point fstype device [device2]
#Gionee lingfen 20120716 add for CR00651943 start
#this is map from /proc/dumchar_info
/boot emmc boot
/cache ext4 /dev/block/mmcblk0p7
/data ext4 /dev/block/mmcblk0p8
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sdcard2 vfat /dev/block/mmcblk0p9
/system ext4 /dev/block/mmcblk0p6
#Gionee lingfen 20120716 add for CR00651943 end

Better Mobile App

welcome