ameer1234567890
commented
11 years ago Starting recovery on Wed Jul 3 21:11:36 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
Welcome to 4EXT Recovery Touch
I:start load volumes..
by madmaxx82
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
Preparing boot.. 0 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p20 (null)
2 /cache ext4 /dev/block/mmcblk0p24 (null)
3 /data ext4 /dev/block/mmcblk0p23 (null)
4 /misc emmc /dev/block/mmcblk0p31 (null)
5 /recovery emmc /dev/block/mmcblk0p21 (null)
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
7 /system ext4 /dev/block/mmcblk0p22 (null)
8 /sd-ext ext4 /dev/block/mmcblk1p2 (null)
I:end load volumes..
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Sun Apr 21 19:36:59 CEST 2013
ro.build.date.utc=0
ro.product.model=HTC EVO 3D
ro.product.brand=generic
ro.product.name=full_shooteru
ro.product.device=shooteru
ro.product.board=shooteru
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=msm8660
ro.build.product=shooteru
net.bt.name=Android
ro.serialno=HT1CXV204492
ro.baseband=11.25.3504.06_M
ro.carrier=HTC-WWE
ro.bootloader=1.49.1107
ro.cid=HTC__001
ro.mid=PG8630000
init.svc.choice_fn=stopped
init.svc.htcbatt=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=92
ext.edition=ng
I:preparing..
Preparing boot.. 1I:prep sys1: 0
Preparing boot.. 1I:preparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
4EXT SmartFlash: disabled
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: enabled
Backups: exclude dalvik-cache: enabled
Preserve theme: enabled
Hide useless directories: enabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 24h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
About to restore from:
2013-07-03.21.48.44_-_cm_shooteru-userdebug_4.2.2_JDQ39E_eng.Johnnyslt.20130630.114951_test-keys
Confirm restore?
Checking MD5 sums...
.android_secure.vfat.tar: OK
boot.img: OK
cache.ext4.tar: OK
data.ext4.tar: OK
recovery.img: OK
sd-ext.ext4.tar: OK
system.ext4.tar: OK
Considering your selection and files contained
in this backup, I'm about to restore:
boot system data cache sd-ext
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Checking backup type..
Tar ext4 backup found..
Restoring system...
I:no fsinfo, or failed to open /sdcard/clockworkmod/backup/2013-07-03.21.48.44_-_cm_shooteru-userdebug_4.2.2_JDQ39E_eng.Johnnyslt.20130630.114951_test-keys//fsinfo
No 4EXT info for that backup found!
Using CWMR5 info if there is any
Otherwise I will assume EXT3 and
store that info for this Backup
If that's wrong, set the filesystem
for this backup to EXT4 from inside
the "TOOLS" menu & restore again!
Setting fsinfo for system to: ext4
Writing 4EXT info for filesystem ext4
Setting fsinfo for data to: ext4
Writing 4EXT info for filesystem ext4
Setting fsinfo for cache to: ext4
Writing 4EXT info for filesystem ext4
Setting fsinfo for sdext to: ext4
Writing 4EXT info for filesystem ext4
Found 4EXT info for /system -> ext4
Creating filesystem with parameters:
Size: 838856704
Block size: 4096
Blocks per group: 32768
Inodes per group: 7328
Inode size: 256
Journal blocks: 3199
Label:
Blocks: 204799
Block groups: 7
Reserved block group size: 0
Created filesystem with 11/51296 inodes and 6429/204799 blocks
warning: wipe_block_device: Discard failed
Checking backup type..
Tar ext4 backup found..
Restoring data...
Found 4EXT info for /data -> ext4
Creating filesystem with parameters:
Size: 1252769792
Block size: 4096
Blocks per group: 32768
Inodes per group: 7648
Inode size: 256
Journal blocks: 4778
Label:
Blocks: 305852
Block groups: 10
Reserved block group size: 0
Created filesystem with 11/76480 inodes and 9592/305852 blocks
warning: wipe_block_device: Discard failed
Checking backup type..
Tar fat32 backup found..
Restoring .android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Checking backup type..
Tar ext4 backup found..
Restoring cache...
Found 4EXT info for /cache -> ext4
Creating filesystem with parameters:
Size: 125816832
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 30717
Block groups: 1
Reserved block group size: 0
Created filesystem with 11/7680 inodes and 1510/30717 blocks
warning: wipe_block_device: Discard failed
Checking backup type..
Tar ext4 backup found..
Restoring sd-ext...
Found 4EXT info for /sd-ext -> ext4
mke2fs 1.41.12 (17-May-2010)
warning: 256 blocks unused.
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
262656 inodes, 1048576 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
32 block groups
32768 blocks per group, 32768 fragments per group
8208 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
Writing inode tables: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.12 (17-May-2010)
Setting default hash algorithm to tea (2)
Restore complete!
Time needed to complete: 700 seconds
reboot now?
When CWM style backups made with Online Nandroid, are restore in 4EXT recovery, 4EXT creates the missing fsinfo file and thus invalidates md5sum file. The restore attempt, however, works perfectly. Only, any future restore attempts of the same backup gives md5sum mismatch error due to the additionally created fsinfo file.
Details about this, with relavant logs, ae provided here: Details, Restore log from 4EXT, Online Nandroid's Log
This issue isn't major, since all CWM backups (even those done with CWM) has the same side-affect.