[help] clockwork mod recovery not working - Android Q&A, Help & Troubleshooting

I:Loaded font:/res/font.datcan't open /dev/tty0: No such file or directorypredefine pixel_format is 4framebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentLoaded (event0): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event2): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event1): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)CWM-based Recovery v6.0.3.0I: using hack for MTK ext4 [email protected]:[MTK]Get size of ext4 device /cache[/dev/block/mmcblk0p7] from fseek =0x7e00000.I:[MTK]Get size of ext4 device /data[/dev/block/mmcblk0p8] from fseek=0x40000000.I:[MTK]Get size of ext4 device /system[/dev/block/mmcblk0p5] from fseek =0x600000.I:[MTK]Get size of ext4 device /cust[/dev/block/mmcblk0p6] from fseek=0x2bc00000.recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /boot emmc /dev/bootimg (null) 02 /cache ext4 /dev/block/mmcblk0p7 (null) 1319895043 /data ext4 /dev/block/mmcblk0p8 (null) 10736107524 /misc emmc /dev/misc (null) 05 /pro_info emmc pro_info (null) 06 /recovery emmc /dev/recovery (null) 07 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 08 /system ext4 /dev/block/mmcblk0p5 (null) 61603849 /cust ext4 /dev/block/mmcblk0p6 (null) 733872128W: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!W:Unable to get recovery.fstab info for /external_sd during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Got arguments from /cache/recovery/commandI:Checking arguments.Warning: No file_contextsI:device_recovery_start()移动叔叔专版www.ydss.cn技术支持: 银狐(yyjdelete)Apr 15 2013 23:19:27Command: "/sbin/recovery""--update_package=CACHE:update.zip"(replacing path "CACHE:update.zip" with"/cache/update.zip")ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=running正在查找刷机包...I:Update location: /cache/update.zip正在打开刷机包...I:read key e=3I:read key e=3I:2 key(s) loaded from /res/keys正在验证刷机包...I:comment is 1738 bytes; signature 1720bytes from endI:whole-file signature verified against key 0I:verify_file returned 0正在安装刷机包...Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 argsrm: /etc: is a directoryabout to run program [/sbin/busybox] with 4 argssh: invalid number 'root'sh: can't kill pid 3468: No such processsh: invalid number 'S'sh: invalid number '/sbin/adbd'sh: invalid number 'recovery'sh: can't kill pid 106: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/adbd'sh: invalid number 'root'sh: can't kill pid 14980: No such processsh: invalid number 'S'sh: invalid number '/sbin/recovery'sh: can't kill pid 109: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/recovery'run_program: child exited with status 1script result was [256]Starting recovery on Wed Sep 25 01:18:52 2013can't open /dev/tty0: No such file or directoryframebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentioctl(): blank: Invalid argumentClockworkMod Recovery v5.5.0.4recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /system ext4 /dev/block/mmcblk0p1 (null) 02 /cache ext4 /dev/block/mmcblk0p2 (null) 03 /misc emmc /dev/block/mmcblk0p3 (null) 04 /staging ext3 /dev/block/mmcblk0p4 (null) 05 /data ext4 /dev/block/mmcblk0p8 (null) 0W: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 /sdcard during fstab generation!W:Unable to get recovery.fstab info for /sd-ext during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Checking arguments.I:device_recovery_start()Command: "/sbin/recovery"ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=runningI:Checking for extendedcommand...I:Skipping execution of extendedcommand, file not found...-- Installing: /sdcard/update.zipFinding update package...I:Update location: /sdcard/update.zipI:using /data/media, no /sdcard found.Opening update package...E:Can't open /sdcard/update.zip(No such file or directory
Card to mount (20s)SDCard mounted..../tmp/recovery.logwas copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.

abhilaab said:
I:Loaded font:/res/font.datcan't open /dev/tty0: No such file or directorypredefine pixel_format is 4framebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentLoaded (event0): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event2): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event1): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)CWM-based Recovery v6.0.3.0I: using hack for MTK ext4 [email protected]:[MTK]Get size of ext4 device /cache[/dev/block/mmcblk0p7] from fseek =0x7e00000.I:[MTK]Get size of ext4 device /data[/dev/block/mmcblk0p8] from fseek=0x40000000.I:[MTK]Get size of ext4 device /system[/dev/block/mmcblk0p5] from fseek =0x600000.I:[MTK]Get size of ext4 device /cust[/dev/block/mmcblk0p6] from fseek=0x2bc00000.recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /boot emmc /dev/bootimg (null) 02 /cache ext4 /dev/block/mmcblk0p7 (null) 1319895043 /data ext4 /dev/block/mmcblk0p8 (null) 10736107524 /misc emmc /dev/misc (null) 05 /pro_info emmc pro_info (null) 06 /recovery emmc /dev/recovery (null) 07 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 08 /system ext4 /dev/block/mmcblk0p5 (null) 61603849 /cust ext4 /dev/block/mmcblk0p6 (null) 733872128W: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!W:Unable to get recovery.fstab info for /external_sd during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Got arguments from /cache/recovery/commandI:Checking arguments.Warning: No file_contextsI:device_recovery_start()移动叔叔专版www.ydss.cn技术支持: 银狐(yyjdelete)Apr 15 2013 23:19:27Command: "/sbin/recovery""--update_package=CACHE:update.zip"(replacing path "CACHE:update.zip" with"/cache/update.zip")ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=running正在查找刷机包...I:Update location: /cache/update.zip正在打开刷机包...I:read key e=3I:read key e=3I:2 key(s) loaded from /res/keys正在验证刷机包...I:comment is 1738 bytes; signature 1720bytes from endI:whole-file signature verified against key 0I:verify_file returned 0正在安装刷机包...Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 argsrm: /etc: is a directoryabout to run program [/sbin/busybox] with 4 argssh: invalid number 'root'sh: can't kill pid 3468: No such processsh: invalid number 'S'sh: invalid number '/sbin/adbd'sh: invalid number 'recovery'sh: can't kill pid 106: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/adbd'sh: invalid number 'root'sh: can't kill pid 14980: No such processsh: invalid number 'S'sh: invalid number '/sbin/recovery'sh: can't kill pid 109: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/recovery'run_program: child exited with status 1script result was [256]Starting recovery on Wed Sep 25 01:18:52 2013can't open /dev/tty0: No such file or directoryframebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentioctl(): blank: Invalid argumentClockworkMod Recovery v5.5.0.4recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /system ext4 /dev/block/mmcblk0p1 (null) 02 /cache ext4 /dev/block/mmcblk0p2 (null) 03 /misc emmc /dev/block/mmcblk0p3 (null) 04 /staging ext3 /dev/block/mmcblk0p4 (null) 05 /data ext4 /dev/block/mmcblk0p8 (null) 0W: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 /sdcard during fstab generation!W:Unable to get recovery.fstab info for /sd-ext during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Checking arguments.I:device_recovery_start()Command: "/sbin/recovery"ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=runningI:Checking for extendedcommand...I:Skipping execution of extendedcommand, file not found...-- Installing: /sdcard/update.zipFinding update package...I:Update location: /sdcard/update.zipI:using /data/media, no /sdcard found.Opening update package...E:Can't open /sdcard/update.zip(No such file or directory)Installation aborted.I:using /data/media, no /sdcard found
Click to expand...
Click to collapse
as it says no sd card is found .. so is your sd card is working fine or not and in cwm check the mounts and storage that the sd card is mounted or not

Related

[Q] CWM problem formatting /data

I flashed CWM 5.5.0.4 a couple weeks ago because I wanted to flash the latest CM9 KANG. I have been having freezing and reboot issues with all the builds I've flashed from Coffeebeans and Pershoot. I noticed the other day in CWM that when it was formatting /data it would do it really quickly but not give me an error. It took longer to format /cache. I found a recovery.log from 3/28 when I flashed Task's v14 ROM. I went through the log and it looks like it's not formatting /data. Here is some of the log:
Starting recovery on Thu Mar 28 23:47:28 2019
framebuffer: fd 4 (1280 x 800)
CWM-based Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) 0
3 /boot emmc /dev/block/mmcblk0p3 (null) 0
4 /system ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /data ext4 /dev/block/mmcblk0p8 (null) 0
7 /preload ext4 /dev/block/mmcblk0p10 (null) 0
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 /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Formatting /cache...
Creating filesystem with parameters:
Size: 469762048
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 1792
Label:
Blocks: 114688
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28672 inodes and 3694/114688 blocks
warning: wipe_block_device: Discard failed
-- Installing: /sdcard/GalaxyTask_14_Slim.zip
Finding update package...
I:Update location: /sdcard/GalaxyTask_14_Slim.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
minzip: Extracted file "/tmp/boot.img"
~~~~~~~~~~~~~~
<== Galaxy Task 14 ==>about to run program [/sbin/busybox] with 3 args
mount: mounting /dev/block/mmcblk0p8 on /data failed: Device or resource busy
After that it finishes installing the ROM without any issues, but I'm worried about why it's not formatting /data.
I'm not sure if this has anything to do with it but when I flashed CMW 5.5.0.4 through Odin I accidentally put it in the bootloader section instead of PDA.
Does anyone have any ideas on this? Should I just Odin back to stock and start over?
Thanks.

[Q] Another bricked Desire X

I will start by excusing for the messed up mail.
Have a HTC Desire X(Y13) that is bricked. It have been unlocked and rooted. Original FW. Got OTA notice yesterday. I reinstalled the recovery and locked it.
After i ran the update and rebooted, it stayed on the welcome/beats screen.
I unlocked it and reinstalled the recovery(CWM).
And now I get the “Can't mount /cache/recovery” ect.
I do have a backup from the CWM. But when trying to restore it. It exits just after it restore the boot.img.
Tried to install different roms. Both cooked and “DesireX1.14.401.1.zip".
Get’s “Installing update”. Assert failed: write_raw_image(“/tmp/boot.img”. “boot”)
I have tried to lock it and restore a stock recovery. And then run the RRU:
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed”
It starts by erasing the user data. Says Starting and Sending. Updating Signature. And after 1min or so it fails with Error 158:Image error.
But it's a Proto ?
I can lock/unlock it. Flash boot.img and recovery’s. Have tried working with the WINTEAM loader. Same problem.
So no matter what I do, I just cant unbrick it. Any ideas on how to do that ?
Could I do an ADB format of the different partitions and flash them? ANY suggestion are welcome.
Log snippets:
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p21 (null) 0
2 /boot emmc /dev/block/mmcblk0p22 (null) 0
3 /cache ext4 /dev/block/mmcblk0p27 (null) 0
4 /data ext4 /dev/block/mmcblk0p26 (null) 0
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
6 /system ext4 /dev/block/mmcblk0p25 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p28 (null) 0
9 /emmc vfat /dev/block/mmcblk0p31 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
magiske said:
I will start by excusing for the messed up mail.
Have a HTC Desire X(Y13) that is bricked. It have been unlocked and rooted. Original FW. Got OTA notice yesterday. I reinstalled the recovery and locked it.
After i ran the update and rebooted, it stayed on the welcome/beats screen.
I unlocked it and reinstalled the recovery(CWM).
And now I get the “Can't mount /cache/recovery” ect.
I do have a backup from the CWM. But when trying to restore it. It exits just after it restore the boot.img.
Tried to install different roms. Both cooked and “DesireX1.14.401.1.zip".
Get’s “Installing update”. Assert failed: write_raw_image(“/tmp/boot.img”. “boot”)
I have tried to lock it and restore a stock recovery. And then run the RRU:
RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed”
It starts by erasing the user data. Says Starting and Sending. Updating Signature. And after 1min or so it fails with Error 158:Image error.
But it's a Proto ?
I can lock/unlock it. Flash boot.img and recovery’s. Have tried working with the WINTEAM loader. Same problem.
So no matter what I do, I just cant unbrick it. Any ideas on how to do that ?
Could I do an ADB format of the different partitions and flash them? ANY suggestion are welcome.
Log snippets:
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p21 (null) 0
2 /boot emmc /dev/block/mmcblk0p22 (null) 0
3 /cache ext4 /dev/block/mmcblk0p27 (null) 0
4 /data ext4 /dev/block/mmcblk0p26 (null) 0
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
6 /system ext4 /dev/block/mmcblk0p25 (null) 0
7 /misc emmc /dev/block/mmcblk0p17 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p28 (null) 0
9 /emmc vfat /dev/block/mmcblk0p31 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
Click to expand...
Click to collapse
You need a jb optimized recovery...
Stereo8 said:
You need a jb optimized recovery...
Click to expand...
Click to collapse
Thanks. Now I can get it up and running. Can I downgrade from here ? Would like to be able to restore my backup ??
/Mads
Yes!
Flowed from my HTC branded muffin...
Surely kernel problem
Hahahahha the same here...For that we need RUU JB aways can fix the mess that we make

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] Can't update CWM : (bad) Installation aborted.

Hi all,
I want to flash CM10.2 for Android 4.3
but, I can't flash any ROM.
when i want to Update CWM, it's impossible.
see the log :
Code:
Starting recovery on Tue Sep 2 12:35:39 2014
framebuffer: fd 4 (480 x 800)
E:unknown volume for path [/system]
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /efs ext4 /dev/block/mmcblk0p1 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p10 (null) 0
7 /preload ext4 /dev/block/mmcblk0p12 (null) 0
8 /emmc vfat /dev/block/mmcblk0p11 (null) 0
9 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
PhilZ Touch 3
CWM Base version: 6.0.1.8
Command: "recovery"
ro.boot.serialno=0009aa09441a2f
ro.sec_debug.enable=0
ro.serialno=0009aa09441a2f
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.debug_level=unknown
ro.emmc_checksum=unknown
ril.dualmode.change=unknown
ro.hardware=smdk4210
ro.revision=14
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp
init.svc.ueventd=running
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
Finding update package...
I:Update location: /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
Opening update package...
E:Can't open /emmc/recovery-clockwork-6.0.4.6-i9100(1).zip
(bad)
Installation aborted.
Have you an idea ?
Sorry for my poor english
Check the md5 of the downloaded zip.
Looks like a corrupted one.
Also make sure you copy / paste the zip on your phone correctly.
Sent from my Nexus 5 using Tapatalk 2
corrupted file
From my own experience it normally is a bad/corrupted file that you downloaded. I've waste hours downloading a file through my phone only to fbd out that I couldn't flash it. Check your downloaded program cause this can affect the result of your download files. I use Internet download manager for windows which is a very useful download manger for all your needs. For the android I used ADM or advance download manager but I suggest using idm on PC insyead .
One rule I always do now is check the archive if they work or unzip in your PC if not then it won't work on your phone when flashing

[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

Categories

Resources