Custom Recovery - Android Q&A, Help & Troubleshooting

I have romdumped my device after searching everwhere and finally found the files. It is very different from the general files and i am confused.
These are the files shown in partitions
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 393216 nandd
93 32 1048576 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 2071552 nandi
179 0 1931264 mmcblk0
179 1 1927164 mmcblk0p1
And mount Points
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:64 /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
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Could you please tell mw how to make a custom recovery for my device.
Device Touchmate M-tab... Basically unherd of and no support anywhere. So please help me.
I had found a recovery builder (clockwork mod builder) but dont know how to use it. And i am confused abt the recovery.fstab.
Thankyou

Related

Help porting CWM Recovery to Lenovo Ideapad K1

Greetings,
I am looking for assistance trying to port CWM recovery to the Lenovo K1. At this point I have attempted to modify the recovery.fstab and compile a CWM recovery.img from the cm7 gingerbread branch. After flashing the new recovery.img (using the steps outlined in the rootzwiki.com 'Messy' guide) the recovery keycombo (Vol+ and Power) or running 'adb reboot recovery' result in just rebooting right back into the OS. Does anyone know of a way to debug this (i.e. logs to look at?)
I'm probably editing the recovery.fstab wrong. Here's the partitions I think are right so far. The rest is a guessing game based on size.
Any help will be greatly appreciated.
recovery.fstab
# mount point fstype device [device2]
/boot mtd ??
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p7 /dev/block/mmcblk0p8
/misc mtd ??
/recovery mtd ??
/sdcard vfat ??
/system ext4 /dev/block/mmcblk0p3
/sd-ext yaffs2 ??
This is the output from mount
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data/temp ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/mmcblk0p8 /data/media/lenovo_media ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
Output from 'cat /proc/partitions'
major minor #blocks name
179 0 31259648 mmcblk0
179 1 5120 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 409600 mmcblk0p3
179 4 131072 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 143360 mmcblk0p6
179 7 27479552 mmcblk0p7
259 0 1024000 mmcblk0p8

[Q] Need some help with partitions

This is my portion layout:
$ su
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,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
and
$ su
# cat /proc/partitions
major minor #blocks name
137 0 513024 bml0/c
137 1 1536 bml1
137 2 768 bml2
137 3 768 bml3
137 4 17920 bml4
137 5 12800 bml5
137 6 768 bml6
137 7 6144 bml7
137 8 2048 bml8
137 9 10240 bml9
137 10 10240 bml10
137 11 768 bml11
137 12 173568 bml12
137 13 173056 bml13
137 14 102400 bml14
179 0 1955840 mmcblk0
179 1 1955775 mmcblk0p1
138 12 166912 stl12
138 13 166400 stl13
138 14 97280 stl14
#
I am trying to put system and boot.img!
I tried dd if=/dev/block/stl12 of=/sdcard/system.img and it shows a pound at the end I check my sdcard and there is nothing there? Is there something I'm doing wrong?

How big are the internal file systems of the phone?

Can someone run "df" command and list the internal file systems?
There you go:
Filesystem Size Used Free Blksize
/dev 389M 84K 389M 4096
/mnt/asec 389M 0K 389M 4096
/mnt/obb 389M 0K 389M 4096
/system 1G 1006M 505M 4096
/data 11G 1G 9G 4096
/cache 1007M 17M 990M 4096
/efs 19M 8M 11M 4096
/mnt/sdcard 11G 1G 9G 4096
/mnt/extSdCard 14G 96K 14G 32768
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
Here is also the mount-command:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:17 /mnt/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

Recovery, Kernel, Data, Cache partition locations?

Has anyone figured out the block location for recovery, Kernel, Data, and cache partitions for the verizon phone? Are they different from carrier to carrier? I know we have the system partition. I would like to start making ODIN packages for the noobs and was wondering if anyone has stumbled across these?? Thanks
http://forum.xda-developers.com/showthread.php?t=1771336
I think that may answer your questions.
But...
It seems that flashing something with Odin that isn't signed by Samsung will cause the binary counter to increase.
I work for warranty for 1 of the big 4 and I can assure you that no one at the phone company can see your binary counter. The refurbishment processor can't even see it. The only one the could check is Samsung in Korea. Lol. If your phone makes it back to Samsung Korea and they see the binary counter then they will bill it back to the carrier and not the customer.
Sent from my SCH-I535 using xda app-developers app
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p14 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p16 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /mnt/extSdCard exfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0
Size Used Free Blksize
/dev 829M 84K 829M 4096
/mnt/asec 829M 0K 829M 4096
/mnt/obb 829M 0K 829M 4096
/system 1G 1023M 453M 4096
/data 26G 4G 22G 4096
/persist 7M 4M 3M 4096
/cache 826M 14M 812M 4096
/efs 13M 4M 8M 4096
/tombstones 7M 4M 3M 4096
/firmware 63M 42M 21M 16384
/mnt/sdcard 26G 4G 22G 4096
/mnt/extSdCard 59G 2G 56G 131072
A formatted version of this file is attached.
ChitownWingMan said:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p14 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p16 /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /mnt/extSdCard exfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0
Size Used Free Blksize
/dev 829M 84K 829M 4096
/mnt/asec 829M 0K 829M 4096
/mnt/obb 829M 0K 829M 4096
/system 1G 1023M 453M 4096
/data 26G 4G 22G 4096
/persist 7M 4M 3M 4096
/cache 826M 14M 812M 4096
/efs 13M 4M 8M 4096
/tombstones 7M 4M 3M 4096
/firmware 63M 42M 21M 16384
/mnt/sdcard 26G 4G 22G 4096
/mnt/extSdCard 59G 2G 56G 131072
A formatted version of this file is attached.
Click to expand...
Click to collapse
SEXUAL!!!! Thanks!!!

{help needed} cannot find boot/recovery partition

i got the cat /proc/mounts here -
Code:
[email protected]:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/nandi /oem cramfs ro,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 ro,relatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal
_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journa
l_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=
ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/extsd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.gameinsight.mycountry-1 vfat ro,dirsync,nosuid,nod
ev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocha
rset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.vividgames.speedwaygp2012-1 vfat ro,dirsync,nosuid
,nodev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,i
ocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
can any one tell me from this which is the boot and recovery partition?
anyone please???
michael.the.don said:
i got the cat /proc/mounts here -
can any one tell me from this which is the boot and recovery partition?
Click to expand...
Click to collapse
/proc/mounts only shows currently mounted partitions, and not boot neither recovery are ever mounted. Instead check either /proc/mtd (for NAND) or in the partition table (for MMC, use fdisk).
If NAND, there's no guarantee the boot loader exposes those partitions to the kernel at all, though.
i tried using /proc/mtd but it says file missing.
how to use fdisk?
i tried using /proc/partitions
it gives me-
[email protected]:/ # cat /partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 5992448 nandj
179 0 15674368 mmcblk0
179 1 15670272 mmcblk0p1
michael.the.don said:
i tried using /proc/mtd but it says file missing.
how to use fdisk?
i tried using /proc/partitions
it gives me-
[email protected]:/ # cat /partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 2048 nandb
93 16 32768 nandc
93 24 262144 nandd
93 32 1048576 nande
93 40 1024 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 5992448 nandj
179 0 15674368 mmcblk0
179 1 15670272 mmcblk0p1
Click to expand...
Click to collapse
Good enough, now you can start mapping all your partitions. Compare this to the mount list, and mark e.g. nande as data, etc. After a while you'll get a few unknown left, potential candidates for boot and recovery you can examine more carefully.
thanks very much.
michael.the.don said:
thanks very much.
Click to expand...
Click to collapse
I'd guess nandc and nandg, they seems about the right size and not mounted. dd them to a file and examine them if they've got the format mkbootimg produces. Those files should begin with "ANDROID!".
# dd if=/dev/block/nandg of=/sdcard/isthisboot.img

Categories

Resources