Database Users

[backup] HELP! {SL101}

http://pastebin.com/n8p5CUxf
Notable lines include
Code:
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!
and
Code:
E:unknown volume for path [/sdcard]
E:unknown volume for path [/sdcard/clockworkmod/backup/2013-02-08.01.50.38]
Can't mount backup path.
and finally
Code:
# mount
rootfs on / type rootfs (rw)
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)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /sdcard type ext3 (rw,relatime,errors=continue,barrier=0,data=writeback)
fyi, I mounted the external sd card on /sdcard to try a backup, but alas.. it fails.

[Q] (Q) Failing backups and restore

I apologize if I've overlooked something simple here, but I am unable to restore my backups. I have swapped to PhilZ Advanced Touch CWM Recovery 6.0.3.7 newly posted in the Android Development Sub Forum.
I believe the error lies in that, for some reason, the external sd card is included in the data partition size calculation (I'm shooting in the dark here but when performing a backup it says needed free space is 21401 MB...I have a 16gb external sd card in the phone). The backups complete with CWM and only take up approx. 1500 MB.
When restoring any of the previously created backups, they all fail at the point of the /data partition. Is there some easy fix for this moving forward (maybe something simple I can change in one of the dumped backup files)? Something I need to reformat?
FWIW I had this problem of 21 GB backup size with TWRP 2.5 as well (yet TWRP fails because it does not continue without the necessary free space).
Any insight would be most appreciated!
Are the errors contained the log typical or do they point out something obvious that needs attention?
Thanks,
Joof
Here are the relevant pieces from the log of the backup being performed....not sure how to grab one from the failed restore and would prefer not to as I have to end up re-flashing the phone
------------------------
Starting recovery on Tue Oct 1 23:30:13 2013
(UTC)
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
CWM Advanced Edition 5
CWM Base version: v6.0.3.7
I:Build version: 5.15.0 - cm_xt907
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
2 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system (null) 0
3 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache (null) 0
4 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata (null) -16384
5 /sdcard datamedia /dev/null (null) 0
6 /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /logo emmc /dev/block/platform/msm_sdcc.1/by-name/logo (null) 0
8 /modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem (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 /preload during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:using /data/media/0 for /sdcard
Irocessing arguments.
I:Checking arguments.
Warning: No file_contexts
I:Warning: No file_contexts
I:device_recovery_start()
I:Cannot open /data/philz-touch/philz-touch_5.ini
I:nandroid_compression set to default (fast)
I:Cannot open /data/philz-touch/philz-touch_5.ini
I:nandroid_md5sum set to default (1)
I:Cannot open /data/philz-touch/philz-touch_5.ini
I:show_nandroid_size_progress set to default (1)
Command: "/sbin/recovery"
ro.boot.hardware=qcom
....
....
(REMOVED FOR BREVITY)
I:Checking for extendedcommand & OpenRecoveryScript...
I:Skipping execution of extendedcommand, file not found...
I:Skipping execution of OpenRecoveryScript, file not found...
I:ro.modversion=pa_scorpionmini-3.99-RC2-30SEP2013-084601
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
I:Checking needed space for backup '/external_sd/clockworkmod/backup/2013-10-01.23.30.25_pa_scorpionmini-3.99-RC2-30SEP2'
E:Failed to find partition size '/boot'
I:/system backup size (stat)=430Mb
I:/cache backup size (stat)=105Mb
I:/data: tot size=4784Mb, free=3600Mb, backup size=21401Mb, used=21709Mb, media=308Mb
I:/external_sd/.android_secure backup size=0Mb
>> Free space: 6414Mb (42%)
>> Needed space: 21937Mb
>> Unknown partitions size (1): - /boot
>> Backing up /boot...
Backing up boot image...
Backup of boot image completed.
Volume not found! Skipping backup of /recovery...
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
>> Backing up /system...
(APPS LISTED...REMOVED FOR BREVITY)
Backup of system completed.
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
>> Backing up /data...
(REMOVED FOR BREVITY)
Backup of data completed.
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
>> Backing up /external_sd/.android_secure...
Backup of .android_secure completed.
I:setting up /data/media(/0) for /sdcard.
I:using /data/media/0 for /sdcard
>> Backing up /cache...
(REMOVED FOR BREVITY)
Backup of cache completed.
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...

Well fastboot flashing stock recovery and doing factory reset/data/cache wipe fixed it. I guess this is not a common issue but thought I'd share my remedy.
Sent from my XT907 using Tapatalk 2

Glad to hear you got your phone working. Just curious, are you now using Philz recovery?
Sent from my XT901 using Tapatalk 4

Thanks!
And Yes. Official philz touch.
I just got this device last week and unlocked the boot loader. I had some issues loading the AOKP 4.3 (boot loops and such even with doing 3x wipes of everything). I eventually had it running smoothly and decided to try the other offerings which is where I discovered this weird backup file size.
But a random post made today in the pacman ROM thread led me to try stock recovery.
Sent from my XT907 using Tapatalk 2

[Q] Have IMEI, SN, and I can backup /EFS. Still unable to mount /EFS (With CWM log)

Greetings,
Title says all, I'm posting the log from CWM.
I tried flashing lots of fw's. And this fix(http://forum.xda-developers.com/showthread.php?t=2507403)
before and after factory reset, removing battery between. Out of clues
Nothing seems to be working for me. Since I first flashed a ROM I could never get network/lockscreen back
Can anyone help me find whats happening with my device?
Starting recovery on Thu Jan 8 23:58:37 1970
framebuffer: fd 4 (1080 x 1920)
min_x_swipe_px=240,min_y_swipe_px=120
CWM-based Recovery v6.0.4.5
Compiled by Xiaolu(20131122)
rm: can't remove '/system/recovery-from-boot.p': No such file or directory
Swipe up/down to change selections.
Swipe to the right for enter.
Swipe to the left for back.
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot 0
1 /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery 0
2 /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system 0
3 /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata 0
4 /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache 0
5 /efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs 0
6 /sdcard datamedia /dev/null 0
7 /external_sd auto /dev/block/mmcblk1 0
8 /storage/usbdisk1 auto /dev/block/sda 0
9 /storage/usbdisk2 auto /dev/block/sdb 0
10 /tmp ramdisk ramdisk 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 /preload during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard /external_sd 0
I:110 0 sda /storage/usbdisk1 0
I:110 0 sdb /storage/usbdisk2 0
I:200 0 Volumes listed.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
...
...
...
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/efs on /efs failed: Invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/efs (File exists)
Error mounting /efs!
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/efs on /efs failed: Invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/efs (File exists)
Error mounting /efs!
I:using /data/media/0 for /sdcard.
Any clues?

Install busybox to get EFS back via CWM.
user @brockyneo had the same issue a few days ago, couldn't restore EFS until he installed busybox
http://forum.xda-developers.com/showthread.php?t=2546724&page=3
It may help with the lockscreen issue.

radicalisto said:
Install busybox to get EFS back via CWM.
user @brockyneo had the same issue a few days ago, couldn't restore EFS until he installed busybox
http://forum.xda-developers.com/showthread.php?t=2546724&page=3
It may help with the lockscreen issue.
Click to expand...
Click to collapse
Thanks a lot, I have asked brock for more detailed information about his solution. I hate messing with EFS, before I restore I want to make one more backup via terminal, I don't know exactly if he did the backup via terminal in his case.

I fixed my phone after one sad week of no networks! I'm so happy!
I used the batch script to restore my EFS via ODIN. and in CWM i was able to mouunt /efs.
Then I did a reset flashed clean ROM and it showed the SIM dialog and lockscreen started to work.
Thanks a lot!

Help . no internet i will dieeee

my data network doesnt connect . i can call and imemi working but H doesnt showing in status bar .
im using cm7 and cm7 kernel ( i changed kernel but same )
rom manager gave this
rom manager said me an error found.and gave this__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!Starting recovery on Sat Aug 2 22:35:33 2014framebuffer: fd 4 (240 x 320)CWM-based Recovery v6.0.5.3recovery filesystem table=========================0 /system yaffs2 system 01 /cache yaffs2 cache 02 /data yaffs2 userdata 03 /storage/sdcard0 auto /dev/block/mmcblk0 04 /sd-ext ext4 /dev/block/mmcblk0p2 05 /boot mtd boot 06 none swap /dev/block/zram0 07 /tmp ramdisk ramdisk 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 /external_sd during fstab generation!I:Completed outputting fstab.I:Connected to Vold..I:110 0 sdcard0 /storage/sdcard0 1-I:200 0 Volumes listed.Irocessing arguments.I:Cannot load volume /misc.I:Cannot load volume /misc.I:Checking arguments.I:device_recovery_start()Command: "/sbin/recovery"ro.cm.device=totororo.cm.display.version=11.0-20140801ro.cm.version=11-20140801-NIGHTLY-totororo.cm.releasetype=NIGHTLYro.sf.lcd_density=120ro.com.google.clientidbase=android-googlero.com.google.networklocation=1ro.com.google.locationfeatures=1ro.com.android.dateformat=MM-dd-yyyyro.com.android.dataroaming=falsero.com.android.wifi-watchlist=GoogleGuestro.ril.hsxpa=1ro.ril.disable.power.collapse=0ro.ril.gprsclass=10ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.htmlro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.htmlro.boot.emmc=0ro.boot.console=ttyS0ro.emmc=0ro.vold.umsdirtyratio=20ro.wifi.channels=ro.allow.mock.location=0ro.board.platform=bcm21553ro.build.id=KTU84Qro.build.date=Sat Aug 2 01:34:24 CEST 20

Are you using the correct APN?

Its most probably because your network drivers have died I had the same problem when I was using H8,and you will have to first return to stock for the drivers to be restored.Then you can flash any rom you like.

can you help me? me found The reason why the stop boot logo cannot into the cwm

model ：samsung rossaltectc
cm version : cm11
When stop in the boot logo , i can adb pull /emp/recovery.log
log content :
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Wed Jan 1 01:10:28 2014
failed to mmap framebuffer: Invalid argument
CWM-based Recovery v6.0.5.1
recovery filesystem table
=========================
0 /efs ext4 /dev/block/mmcblk0p13 0
1 /boot emmc /dev/block/mmcblk0p16 0
2 /recovery emmc /dev/block/mmcblk0p17 0
yes , he display failed to mmap framebuffer: Invalid argument
I don't know what's going on
I google many times , but did not find any related issues
can you help me :crying:
me need you Guys