Starting recovery on Sat Mar 22 16:04:31 2014
framebuffer: fd 4 (720 x 1280)
CWM-based Recovery v6.0.3.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p16 (null) 0
2 /cache ext4 /dev/block/mmcblk0p18 (null) 0
3 /data ext4 /dev/block/mmcblk0p21 (null) -16384
4 /recovery emmc /dev/block/mmcblk0p13 (null) 0
5 /misc emmc /dev/block/mmcblk0p11 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /system ext4 /dev/block/mmcblk0p17 (null) 0
8 /sys_boot vfat /dev/block/mmcblk0p3 (null) 0
9 /FOTA emmc /dev/block/mmcblk0p19 (null) 0
10 /sdcard vfat /dev/block/mmcblk0p20 (null) 0
11 /sdcard1 vfat /dev/block/mmcblk0p20 (null) 0
12 /persist ext4 /dev/block/mmcblk0p15 (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 /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:Checking arguments.
Warning: No file_contexts
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
abrove are some code . i do not know where to modify anybody can give me some adverse it might be great
Related
Hi guys, please anyone help me have a working custom recovery for my local device.
Here are some of my device info
Starting recovery on Sun Jan 6 00:46:45 1980
framebuffer: fd 4 (480 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p16 (null) 0
2 /cache ext4 /dev/block/mmcblk0p18 (null) 0
3 /data ext4 /dev/block/mmcblk0p21 (null) -16384
4 /recovery emmc /dev/block/mmcblk0p13 (null) 0
5 /misc emmc /dev/block/mmcblk0p11 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /system ext4 /dev/block/mmcblk0p17 (null) 0
8 /sys_boot vfat /dev/block/mmcblk0p3 (null) 0
9 /FOTA emmc /dev/block/mmcblk0p19 (null) 0
10 /sdcard1 vfat /dev/block/mmcblk0p20 (null) 0
Click to expand...
Click to collapse
This the link on it's full specs
http://www.cherrymobile.com.ph/products/smart-social/flare-2x
Hi,
this is recovery.log
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
No files found.
No files found.
I:Can't partition unsafe device: /dev/block/mmcblk1p1
RenorainChile said:
Hi,
this is recovery.log
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
No files found.
No files found.
I:Can't partition unsafe device: /dev/block/mmcblk1p1
Click to expand...
Click to collapse
Other dat error's
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /qcsblhd_cfgdata emmc /dev/block/mmcblk0p1 (null) 0
2 /qcsbl emmc /dev/block/mmcblk0p2 (null) 0
3 /amss emmc /dev/block/mmcblk0p3 (null) 0
4 /oemsbl emmc /dev/block/mmcblk0p5 (null) 0
5 /emmcboot emmc /dev/block/mmcblk0p6 (null) 0
6 /ssd emmc /dev/block/mmcblk0p7 (null) 0
7 /boot emmc /dev/block/mmcblk0p8 (null) 0
8 /cefs1 emmc /dev/block/mmcblk0p10 (null) 0
9 /cefs2 emmc /dev/block/mmcblk0p11 (null) 0
10 /system ext4 /dev/block/mmcblk0p12 (null) 0
11 /data ext4 /dev/block/mmcblk0p13 (null) 0
12 /persist ext4 /dev/block/mmcblk0p14 (null) 0
13 /cache ext4 /dev/block/mmcblk0p15 (null) 0
14 /recovery emmc /dev/block/mmcblk0p16 (null) 0
15 /misc emmc /dev/block/mmcblk0p17 (null) 0
16 /FOTA emmc /dev/block/mmcblk0p18 (null) 0
17 /splash emmc /dev/block/mmcblk0p19 (null) 0
18 /sdcard2 vfat /dev/block/mmcblk0p20 (null) 0
19 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 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 /sd-ext during fstab generation!
Hi,
I have a sony tablet s and it froozed in google chrome and never came back to life.
It's stuck in sony logo. I have the most recent firmware installed with condi tool with root.
Here's my recovery log:
Starting recovery on Sun May 18 01:09:57 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsdcard vfat /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 /datapp/vendor/vendor0.img (null) 0
17 /vendor1 ext4 /datapp/vendor/vendor1.img (null) 0
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TISU0077
ro.build.display.id=TISU0077
ro.build.version.incremental=120410009
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue Apr 10 01:43:14 JST 2012
ro.build.date.utc=1333989794
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build6
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_002
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=nbx03
ro.build.description=SYS_002-user 4.0.3 TISU0077 120410009 test-keys
ro.build.fingerprint=Sony/SYS_002/nbx03:4.0.3/TISU0077/120410009:user/test-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
windowsmgr.max_events_per_sec=120
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
drm.service.enabled=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0.3_r0
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna.dtcp_pext=0
ro.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx03_011-ota-121116066.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111104048 -> 121116066
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
Erohibit update as a result of checking version or base sku
Installation aborted.
Starting recovery on Sun May 18 01:10:52 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsdcard vfat /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 /datapp/vendor/vendor0.img (null) 0
17 /vendor1 ext4 /datapp/vendor/vendor1.img (null) 0
My region is Portugal, and i tried many firmware files out here, but in recovery none of them are installed.
Anyone has a clue what to do?
Thanks
:good:
Oi! Tens o firmwire de origem mas o honeycomb para a nossa maquina?pode resolver...nao encontro isso em lado nenhum e ja foi retirado dos servidores da sony
Sent from my ALCATEL ONE TOUCH 997D using XDA Free mobile app
This is odd: switched phone on this morning and it was stuck at the boot logo. I did a bit of digging around and it looks like the internal memory is corrupt because it is refusing to mount /data or /system.
I am ok doing a kies or odin recovery but before i do it would be nice (not essential) to recover some data. I can get into download and recovery and have tried to mount them manually but it didn't work.
Before I go for the full reset, an ideas on mounting /data?
cheers
m
ps. "boot" not "boo"!
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
ls /dev/block
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
platform
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
cat fstab
/dev/block/mmcblk0p3 /efs ext4 rw
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p10 /preload ext4 rw
/external_sd vfat rw
/usb-otg vfat rw
mount -a
mount: mounting /dev/block/mmcblk0p3 on /efs failed: Invalid argument
mount: mounting /dev/block/mmcblk0p9 on /system failed: Invalid argument
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount: mounting /external_sd on vfat failed: No such file or directory
mount: mounting /usb-otg on vfat failed: No such file or directory
mount -o rw,remount /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount -t ext4 -o rw,remount /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount -t ext4 -o rw /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
Try this: http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Already have plenty of emergency firmwares as per OP - just wondering if it's possible to mount the partitions some other way. However, no worries: gave up and just reloaded one using odin. worked fine.
I'm getting this error while doing mka -j8 bacon:
Code:
File "/home/tanujboy/android/cyanogenmod-12.1/build/tools/releasetools/common.py", line 259, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/dev/block/mmcblk0p22 /system ext4"
build/core/Makefile:1498: recipe for target '/home/tanujboy/android/cyanogenmod-12.1/out/target/product/black/obj/PACKAGING/target_files_intermediates/cm_black-target_files-5fb2ce1c7f.zip' failed
make: *** [/home/tanujboy/android/cyanogenmod-12.1/out/target/product/black/obj/PACKAGING/target_files_intermediates/cm_black-target_files-5fb2ce1c7f.zip] Error 1
make: Leaving directory '/home/tanujboy/android/cyanogenmod-12.1'
Can someone help me out and tell me how to fix this?
This is my recovery.fstab BTW:
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p22 /system ext4
/dev/block/mmcblk0p29 /data ext4
/dev/block/mmcblk0p23 /cache ext4
/dev/block/mmcblk0p24 /persist ext4
/dev/block/mmcblk0p20 /boot emmc
/dev/block/mmcblk0p21 /recovery emmc
/dev/block/mmcblk0p25 /misc emmc
/dev/block/mmcblk1p1 /dev/block/mmcblk1 /external_sd vfat flags=display="Micro SDcard";storage;wipeingui;removable
/dev/block/sda1 /dev/block/sda /usb-otg vfat flags=removable;storage;display=USB-OTG
See this: https://github.com/CyanogenMod/android_build/blob/cm-12.1/tools/releasetools/common.py#L222
Try this:
Code:
/dev/block/mmcblk0p22 /system ext4 ro,barrier=1