Hello guys, i am a new android user. My device (Huawei T8620) running on Android ICS suddenly power off and could not boot back. When i tried updating the firmware it shows error dump txt file
Starting recovery on Wed Jan 4 12:45:22 2012
framebuffer: fd 4 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
app_info item=board_id content=MTK6515_T8620.VerC
BoardType=MTK6515_T8620
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /system ext4 /dev/block/mmcblk0p6 (null) 0
8 /Insdcard vfat /dev/block/mmcblk0p4 (null) 0
I:Boot command: UPDATE:SD
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/command
I:no boot messages
I:check otaupdate is done clear boot message
open /data/recovery/command failed
Entry Force mode SD upgrade........................................... ..........
battery voltage is 4106,that's OK!
sdcard is mounted
Init dload file num=0,filename=/sdcard/dload/update.app
file -/sdcard/dload/update.app size=ffffffff bytes.
Open /sdcard/dload/update.app failed
Init dload file num=1,filename=/sdcard/dload/update_cust.app
file -/sdcard/dload/update_cust.app size=ffffffff bytes.
Open /sdcard/dload/update_cust.app failed
no APP files found in SD card
Exit Force mode SD upgrade........................................... ...........
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
W:Can't unlink /cache/recovery/command
Could you please help me out guys.. i'm stuck! Thanks..and of course my phone is rooted.
SOLVED
Resolved and Running on stock Rom ICS 4.0.3 again.
Related
Hey
I have a init.rc modded so I can have ext2 in my boot.img
But it is not working...
http://pastebin.com/TxixgL3C
line 89 was this:
mount rfs /dev/stl13 /data nosuid nodev check=no
but should become:
mount ext2 /dev/stl13 /data noatime nodiratime nosuid nodev check=no || mount rfs /dev/stl13 /data nosuid nodev check=no
But somehow it is not working and I believe Android takes it for rfs...
If i just replace it with:
mount ext2 /dev/stl13 /data noatime nodiratime nosuid nodev check=no
Everything works fine...
What's wrong?
Hmmm anyone please?
Whatever I seem to try I keep rebooting into recovery. Could someone please help me out? Here's the log:
Starting recovery on Thu Jun 7 01:24:04 2012
framebuffer: fd 4 (480 x 800)
CWM-based Voodoo Lagfix Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /cache rfs /dev/block/stl11 (null)
3 /data rfs /dev/block/stl10 (null)
4 /recovery bml recovery (null)
5 /sdcard vfat /dev/block/mmcblk0p1 (null)
6 /system rfs /dev/block/stl9 (null)
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!
I:Completed outputting fstab.
Irocessing arguments.
mount: mounting /dev/block/stl11 on /cache failed: Invalid argument
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=herring
ro.revision=48
init.svc.recovery=running
init.svc.adbd=running
ro.build.product=herring
ro.product.device=herring
ro.radio.noril=yes
ro.bt.bdaddr_path=/efs/bluetooth/bt_addr
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.telephony.call_ring.multiple=0
ro.nfc.port=I2C
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
What ROM are you running? It might be worth wiping and reinstalling it.
Ah nevermind I fixed it flashing KG4 worked
Where u on mtd and flashed a bml rom thru cwm? Lol
sent from my batcave
Hey guys.
I reccenty flashed my Galaxy note using Root_SuperSU.0.96-Busybox.1.20.2-S2, All went well expect now i cannot install any custom roms.
I have been trying to install Asylum_CM10.1_20130201_n7000 however i keep getting "Status 7, installation aborted"
here is my log:
Starting recovery on Fri Feb 1 09:16:56 2013
[initialize ui and event]
pixel format -> GGL_PIXEL_FORMAT_BGRA_8888
framebuffer: fd 4 (800 x 1280)
[collecting table information]
recovery filesystem table
=========================
0 '/tmp' 'ramdisk' '(null)' '(null)' 0
1 '/efs' 'ext4' '/dev/block/mmcblk0p1' '(null)' 0
2 '/boot' 'emmc' '/dev/block/mmcblk0p2' '(null)' 0
3 '/recovery' 'emmc' '/dev/block/mmcblk0p6' '(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)' -16384
7 '/preload' 'ext4' '/dev/block/mmcblk0p12' '(null)' 0
8 '/sdcard' 'vfat' '/dev/block/mmcblk1p1' '/dev/block/mmcblk1' 0
9 '/sdcard1' 'vfat' '/dev/block/mmcblk0p11' '(null)' 0
emmc_checksum fail.
[initialize init-recovery]
#mount /system
stat() of /dev/block/mmcblk0p9 succeeded on try 1
/system sucessfully mounted
#unmount /cache
/cache sucessfully unmounted
#exec -f /system/bin/e2fsck -v -y /dev/block/mmcblk0p7
e2fsck 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p7: clean, 23/12800 files, 3094/51200 blocks
#insmod -f -v /system/lib/modules/exfat_core.ko
trace: insmod_main: /system/lib/modules/exfat_core.ko
trace: insmod_main: 1
trace: __out_return: _do_insmod :: can't open '/system/lib/modules/exfat_core.ko' (No such file or directory)
#insmod -f -v /system/lib/modules/exfat_fs.ko
trace: insmod_main: /system/lib/modules/exfat_fs.ko
trace: insmod_main: 1
trace: __out_return: _do_insmod :: can't open '/system/lib/modules/exfat_fs.ko' (No such file or directory)
#lsmod
exfat_fs 17079 0 - Live 0xbf013000 (P)
exfat_core 59555 1 exfat_fs, Live 0xbf000000 (P)
#mount /cache
stat() of /dev/block/mmcblk0p7 succeeded on try 1
/cache sucessfully mounted
#ls /cache/recovery/
-rw-r----- root root 9037 2013-02-01 08:57 last_log
-rw-r--r-- root root 43 2013-02-01 08:57 last_install
-rw------- root root 697 2013-02-01 09:16 11-rommanager.sh
-rw------- root root 3100489 2013-02-01 09:16 RomManager.apk
-rw------- root root 156 2013-02-01 09:16 restorerommanager.sh
-rw------- root root 704 2013-02-01 09:16 extendedcommand
-rw------- root root 33 2013-02-01 09:16 .salted_hash
-rw------- root root 34 2013-02-01 09:16 command
#mount /data
stat() of /dev/block/mmcblk0p10 succeeded on try 1
/data sucessfully mounted
#fcut --limited-file-size=64k -f /data/log/recovery_log.txt /tmp/recovery_backup.txt
trace: __out_return: _do_fcut :: failed lstat '/data/log/recovery_log.txt' (No such file or directory)
/system sucessfully unmounted
/cache sucessfully unmounted
/data sucessfully unmounted
running init-recovery time : 0.243s
[collecting command]
stat() of /dev/block/mmcblk0p7 succeeded on try 1
I:Got arguments from /cache/recovery/command
Command: "/sbin/recovery" "--update_package=CACHE:update.zip"
previous_runs = 0
send_intent = (null)
update_package = CACHE:update.zip
att_fota_update = 0
tmo_fota_update = 0
wipe_data = 0, wipe_cache = 0,wipe_sdcard = 0,delete_data = 0,wipe_data_crypto = 0
show_ui_text = 0
update_factory_csc = 0,update_home_csc = 0
carry_out = (null)
(replacing path "CACHE:update.zip" with "/cache/update.zip")
[property list]
ro.boot.serialno=0019f1002f2cae
ro.sec_debug.enable=0
ro.serialno=0019f1002f2cae
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=8
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
init.svc.ueventd=running
init.svc.recovery=running
stat() of /dev/block/mmcblk0p1 succeeded on try 1
[Installing package]
-- Installing package...
Finding update package...
I:Update location: /cache/update.zip
Opening update package...
I:2 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
signed len : 1879580
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
sh: you need to specify whom to kill
sh: invalid number 'root'
sh: can't kill pid 21096: No such process
sh: invalid number 'S'
sh: invalid number '/sbin/recovery'
run_program: child exited with status 1
script result was [256]
Starting recovery on Fri Feb 1 09:17:00 2013
framebuffer: fd 4 (800 x 1280)
ClockworkMod Recovery v6.0.1.2
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.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.serialno=0019f1002f2cae
ro.sec_debug.enable=0
ro.serialno=0019f1002f2cae
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=8
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
init.svc.ueventd=running
init.svc.recovery=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
05c6f41850f6980d080d08215614ab6e
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.5.1.7");
ui_print("1 February 2013");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
mount("/system");
run_program("/sbin/chmod", "+x", "/tmp/recovery/11-rommanager.sh");
run_program("/tmp/recovery/11-rommanager.sh", "place");
run_program("/sbin/umount", "/system");
format("/data");
format("/sd-ext");
assert(install_zip("/sdcard/Asylum_CM10.1_20130201_n7000.zip"));
format("/cache");
mount("/system");
run_program("/sbin/chmod", "+x", "/tmp/recovery/restorerommanager.sh");
run_program("/tmp/recovery/restorerommanager.sh");
run_program("/sbin/umount", "/system");
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.5.1.7
1 February 2013
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p7 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/mmcblk0p9 on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
Formatting /data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Wipe via secure discard suppressed due to bug in EMMC firmware
Formatting /sd-ext...
-- Installing: /sdcard/Asylum_CM10.1_20130201_n7000.zip
Finding update package...
I:Update location: /sdcard/Asylum_CM10.1_20130201_n7000.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" ||
getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" ||
getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" ||
getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" || getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" || getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" || getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
E:Error in /sdcard/Asylum_CM10.1_20130201_n7000.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Asylum_CM10.1_20130201_n7000.zip")
Thanks for your help!
Is it ok to use mmcblk in src links when building cyanogenmod?
I forgot to change them and its bulding for a few hours now. Should I stop it?
My fstab looks like this:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mmcblk0p24 /system ext4 ro,errors=panic wait
/dev/block/mmcblk0p27 /data ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check,encryptable=footer,length=-16384
/dev/block/mmcblk0p25 /cache ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,check
/dev/block/mmcblk0p13 /efs ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait
/dev/block/mmcblk0p22 /persist ext4 nosuid,nodev,data=ordered,nodelalloc wait
/dev/block/mmcblk0p1 /firmware emmc ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/mmcblk0p2 /firmware-modem emmc ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/mmcblk0p16 /boot emmc defaults defaults
/dev/block/mmcblk0p17 /recovery emmc defaults defaults
/dev/block/mmcblk0p26 /preload ext4 defaults defaults
# VOLD
/devices/soc.0/7864900.sdhci/mmc_host/mmc* auto vfat default voldmanaged=extSdCard:auto,noemulatedsd
/devices/platform/msm_hsusb_host/usb*sda auto vfat default voldmanaged=UsbDriveA:auto
/devices/platform/msm_hsusb_host/usb*sdb auto vfat default voldmanaged=UsbDriveB:auto
/devices/platform/msm_hsusb_host/usb*sdc auto vfat default voldmanaged=UsbDriveC:auto
/devices/platform/msm_hsusb_host/usb*sdd auto vfat default voldmanaged=UsbDriveD:auto
/devices/platform/msm_hsusb_host/usb*sde auto vfat default voldmanaged=UsbDriveE:auto
/devices/platform/msm_hsusb_host/usb*sdf auto vfat default voldmanaged=UsbDriveF:auto
Hi,
Try reading and posting your question here:
http://forum.xda-developers.com/showthread.php?t=667298
The experts there may be able to help.
Good luck!
Recently I installed DotOS on my Samsung SM-J320F. All good but internal space was reduced. This phone have 8 GB but I receive this when I run df:
~ # ←[6ndf
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 696068 204 695864 0% /dev
tmpfs 696068 28 696040 0% /tmp
/dev/block/mmcblk0p27
5027508 4601436 409688 92% /data
/dev/block/mmcblk0p27
5027508 4601436 409688 92% /sdcard
/dev/block/mmcblk0p24
197472 276 193100 0% /cache
/dev/block/mmcblk1p1 24862304 13880880 10981424 56% /extSdCard
~ # ←[6n
Also Windows says I have only 4.79GB
How can I recover 3GB of space?
No one know to solve my problem ?