Database Info

[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log

hi guys, this problem was solved, unexpectedly.
after read guhl99's post in Thread: PSA: Rooting methods and recently discovered dangersthread,
i finally confirm that my htc DS was bricked by an accidentally freeze and the immediately battery pulled-out-&-pushed-in unstably.
the eMMC-chip(marked as SAMSUNG104, KLM4G2DEJE A001, FDAE15PC) was completely dead,
i made a replacement with a new one(made by Sandisk serial:SEM04G), and then everything goes on good.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Thanks to" the design of the battery compartment door, the battery pullout-pushin becomes running-risks.
Make sure there's NOT any tiny battery move when you flipping the compartment door from the side.
Make sure disconnect the battery and DS itself quickly & stably as soon as you could.
Make sure there's at least 10 seconds between battery pullout and pushin.
"How can I be sure if it's a hw problem? I mean, it looks like one, but I would like to be sure..."
please check #27 http://forum.xda-developers.com/showpost.php?p=16135893&postcount=27
A eMMC design flaw, Confirming info from htc-offical (thanks apairofscissors)
http://forum.xda-developers.com/showpost.php?p=20163494&postcount=23
=============Debug Procedure=============
Here are 3 parts in this post.
Actually, it's not that long,
and the most important info is in 8. [ adb shell ]
================Background================
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.00RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2001,14:58:38
ClockworkMod Recovery 3.2.0.0
a busybox within
================what happend================
while installing some apps from the market, DS was stuck at a app called "push ups".
i pulled out battery and reboot, and there came loopboot.
got in Recovery, it promts
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
================things i did================
1. [ wipe data/factory reset]
Code:
Formating /data...
black splash screen, and then
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
[ wipe cache ]
Code:
Formating /cache...
Cache wipe complete.
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
2. [ install zip from sdcard ]
Code:
-Checking Model ID
-success!
-Model ID - HTC sage
Now flashing
E:Error in /sdcard/*******.zip
(Status 1)
Installation aborted.
3. [ backup and restore ]
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoreing system....
Error while formatting /system!
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
4. [ RUU+Goldencard ]
Goldencard is good, in FASTBOOT USB mod,
passed the (version) checking, updating 1.28.401.1 to 1.47.950.3, but stuck at
Code:
rebooting bootloader ......
upgrading ROM image in your Android Phone...
Please do NOT disconnect USB cable nor run any program.
5. [ ROM.zip->PG88IMG.zip ]
ROM.zip was picked-up from RUU, renamed to PG88IMG.zip, copied to sdcard,
reboot to HBOOT, and it unzip the pack normally, then stuck at updating screen, more than 1 hour.
Code:
HBOOT
[INDENT]Parsing...[SD ZIP]
[1] BOOTLOADER -updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SLPASH1
[6] USERDATA
[7] TP
[8] DADIO_V2
[9] RADIO_CUST
Do you want to start update?
[/INDENT]
6. [ PG88IMG.zip for Recovery/Radio ]
HBOOT asks do you wanna upgrade, click VOL-up, then stuck at updating screen
Code:
HBOOT
[INDENT]Parsing...[SD ZIP]
[1] RECOVERY -updating
*********
Updating is in progress...
Do not power off the device!
[/INDENT]
7. [ fastboot ]
Code:
SH********8 Connected.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 38.03.02.15_m.
SPL/hboot version: 0.98.0000.
product: saga.
mid: pg88*****.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
[B]fastboot erase cache[/B]
erasing 'cache'...
[COLOR=red]erasing 'cache'... FAILED (command write failed (Unknown error))[/COLOR]
8. [ adb shell ]
DS has 2 storages:
eMMC-chip inside, /system /data /cache are mounted to mmcblk0p25, mmcblk0p26, mmcblk0p27;
SDCard removable /sdcard is mounted to mmcblk1p1.
i connect the my phone(DS-brick) through adb-shell, and compared with my friend's (DS-good), here are the prompts:
DS-good shows
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,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/[COLOR=blue]mmcblk0p25 on /system type ext3 [/COLOR](rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/[COLOR=blue]mmcblk0p26 on /data type ext3[/COLOR] (rw,relatime,errors=continue,barrier=0,
data=writeback)
/dev/block/[COLOR=blue]mmcblk0p27 on /cache type ext3 [/COLOR](rw,nodev,noatime,nodiratime,errors=co
ntinue,barrier=0,data=writeback)
/dev/block/[COLOR=blue]mmcblk1p1 on /sdcard type vfat[/COLOR] (rw,relatime,fmask=0000,dmask=0000,all
ow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-
ro)
DS-brick shows
Code:
/dev/block/[COLOR=blue][COLOR=red][B]mmcblk0p27 on /cache type ext4[/B][/COLOR] [/COLOR](ro,nodev,noatime,nodiratime,barrier=1
,data=ordered)
~ # mount system
mount: mounting /dev/block/mmcblk0p25 on /system [COLOR=red][B]failed: Invalid argument[/B][/COLOR]
~ # mount data
mount: mounting /dev/block/mmcblk0p26 on /data [COLOR=red][B]failed: Invalid argument[/B][/COLOR]
it means the filesystem on eMMC was accidentally broke down. so, im trying to restore the filesystem, and get these:
list the eMMC-chip partition info
Code:
~ # fdisk -l /dev/block/[B]mmcblk0[/B]
fdisk -l /dev/block/mmcblk0
[B][COLOR=red]fdisk: can't open '/dev/block/mmcblk0': I/O error[/COLOR][/B]
format /cache with type ext3
Code:
~ # mke2fs -j /dev/block/[COLOR=blue]mmcblk0p27[/COLOR]
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
76912 inodes, 307196 blocks
15359 blocks (5.00%) reserved for the super user
[B]First data block=1[/B]
Maximum filesystem blocks=67633152
38 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=red][B]ext2fs_mkdir: Attempt to read block from filesystem [/B][/COLOR]
[COLOR=red][B]resulted in short read while creating root dir[/B][/COLOR]
format /system with type ext3
Code:
~ # mke2fs -j /dev/block/[COLOR=blue]mmcblk0p25[/COLOR]
mke2fs -j /dev/block/mmcblk0p25
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
35760 inodes, 142847 blocks
7142 blocks (5.00%) reserved for the super user
[B]First data block=0[/B]
Maximum filesystem blocks=146800640
5 block groups
32768 blocks per group, 32768 fragments per group
7152 inodes per group
Superblock backups stored on blocks:
32768, 98304
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted [/COLOR][COLOR=blue]in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=blue][B]Creating journal (4096 blocks): done[/B][/COLOR]
[COLOR=blue][B]Writing superblocks and filesystem accounting information: done[/B][/COLOR]
[COLOR=blue][B]This filesystem will be automatically checked every 39 mounts or[/B][/COLOR]
[COLOR=blue][B]180 days, whichever comes first. Use tune2fs -c or -i to override.[/B][/COLOR]
format /data with type ext3
Code:
mke2fs -j /dev/block/mmcblk0p26
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
75200 inodes, 300799 blocks
15039 blocks (5.00%) reserved for the super user
[B]First data block=0[/B]
Maximum filesystem blocks=310378496
10 block groups
32768 blocks per group, 32768 fragments per group
7520 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted [/COLOR][COLOR=blue]in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=blue]Creating journal (8192 blocks): done[/COLOR]
[B][COLOR=blue]Writing superblocks and filesystem accounting information: done[/COLOR][/B]
[COLOR=blue][B]This filesystem will be automatically checked every 22 mounts or[/B][/COLOR]
[COLOR=blue][B]180 days, whichever comes first. Use tune2fs -c or -i to override[/B][/COLOR].

Not identical but market related to this thread http://forum.xda-developers.com/showthread.php?t=1141843
Sent from my HTC Desire S using XDA Premium App

Sorry to hear that mate, Have you tried flashing a custom recovery and format the partitions in ext4 format, cause as far as I know DS default partition format is ext4...

zorbakun said:
Sorry to here that mate, Have you tried flashing a custom recovery and format the partitions in ext4 format, cause as far as I know DS default partition format is ext4...
Click to expand...
Click to collapse
thanx for reply...
but my friend's DS shows:
Code:
/dev/block/mmcblk0p25 on /system type [B]ext3[/B] (rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/mmcblk0p26 on /data type[B] ext3 [/B](rw,relatime,errors=continue,barrier=0,
data=writeback)
/dev/block/mmcblk0p27 on /cache type [B]ext3[/B] (rw,nodev,noatime,nodiratime,errors=co
ntinue,barrier=0,data=writeback)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,all
ow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-
ro)

Well, I'm quite sure the DS default partition format is ext4, mine is like wise ext4, you have got nothing to lose there, try to flash that customer recovery and format or convert your phone partitions to ext4, then flash any of the customs roms available around or a RUU if you want.

The easiest way to rectify is to RUU and start over. Unless you enjoy the frustration!

zorbakun said:
Well, I'm quite sure the DS default partition format is ext4, mine is like wise ext4, you have got nothing to lose there, try to flash that customer recovery and format or convert your phone partitions to ext4, then flash any of the customs roms available around or a RUU if you want.
Click to expand...
Click to collapse
thank you guys.
as i wrote above, i did RUU. and stuck at the updating screen.
could zorbakun tell me, how can i format the emmc with ext4(especially to cache)

download this Custom recovery, Flash it and there is an option to format/wipe the partitions in ext4 format or convert current ext3 to ext4, also try to flash one of the custom roms in the development section but first flash the custom recovery.

i ran fastboot oem boot, and got these info:
is there anything wrong about my cid?
Code:
... INFOsetup_tag addr=0xC0000100 cmdline add=0x8D09D070
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x28102
INFOTAG:hero panel = 0x400010
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFOTAG: PS ID = 0x0
INFODevice CID is super CID
INFOCID is super CID
INFOBackup CID is empty
INFOsetting->[COLOR="Red"][B]cid::11111111[/B][/COLOR]
INFOserial number: SH*********8
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =533
INFOactive commandline: board_saga.disable_uart2=0 board_saga.us
INFOb_h2w_sw=0 board_saga.disable_sdcard=0 diag.enabled=0 board_
INFOsaga.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=
INFOtrue androidboot.pagesize=4096 androidboot.baseband=38.03.0
INFO2.15_M androidboot.[COLOR="Red"][B]cid=11111111[/B][/COLOR] androidboot.batt_poweron=goo
INFOd_battery androidboot.carrier=ALL androidboot.mid=PG88*****
INFOandroidboot.keycaps=qwerty androidboot.mode=normal androidbo
INFOot.serialno=SH*********8 androidboot.bootloader=0.98.0000 zy
INFOgote_oneshot=off msm_watchdog.enable=1 kmemleak=off no_conso
INFOle_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOaARM_Partion[7].name=pdata
INFOpartition number=8
INFOValid partition num=8
INFOjump_to_kernel: machine_id(3107), tags_addr(0x4400100), kern
INFOel_addr(0x4408000)
INFO-------------------hboot boot time:80883 msec
FAILED (status read failed (Too many links))
Edit: INFOsetting->cid::11111111 means it's super cid, and super cid is good!

It's the very same thing as what happened to me, thought I haven't done deep debugging like you did and my device is S-ON. I did step 5 and my device froze at updating bootloader too. I guess there is something wrong with the phone, I'm worried about this massive market update issue. Maybe you'll be able to provide some more informations.
Also, I'm very sorry to hear this, I hope you'll be able to fix it asap, as this is very strange issue (how can market or battery pulled out brick phone???).

Numline1 said:
(how can market or battery pulled out brick phone???.
Click to expand...
Click to collapse
indeed!!!!

well, i'm kinda glad i'm not the only one with this problem... so far, the phone is still working and only sometimes crashes, so i can live with it...
i guess replacing the chip as mentioned in the first post requires sending the device to htc... would that cost anything with my xtc-clip-s-offed device? if so, how much? an estimate would be nice...

szallah said:
well, i'm kinda glad i'm not the only one with this problem... so far, the phone is still working and only sometimes crashes, so i can live with it...
i guess replacing the chip as mentioned in the first post requires sending the device to htc... would that cost anything with my xtc-clip-s-offed device? if so, how much? an estimate would be nice...
Click to expand...
Click to collapse
if ur DS is S-OFF and can't be succeed in wipe data/cache, can't mount nor open...
i did this replacement in our local-telecomm-market not htc official service.
that cost me US$60.

Same happened to me DAMMIT !!! What can i do? Tell me

All you need do is reflash Recovery and fresh install your rom. DO NOT RUN FLASH THE Nandroid BACK UP. Use PB88 the method.
Replace the chip? lol.

wait wait wait. I had a problem, that my phone wouldn't boot up after a radio flash. In recovery it said
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I restored a nandroid backup and it booted up, with the new radio (i checked), What should i do now?

There are 2 issues that can cause these errors.
1) Messed up Partition table,
2) Broken eMMC chip (or more specifically, chip controller)
Issue 1 can be fixed by fixing the Partition table, which can be acheived by flashing an RUU.
Issue 2 cannot be fixed. (Unless you're a confident solder-er and know what you're doing, which chip to replace)
It is a hardware issue and your device will have to be returned.
Luckily, We don't know of anyone who has had an issue returning a rooted, s-off device.
There is more information in this thread, as well as how to know definatley whether you have the broken chip or not.
-Nipqer

Nipqer said:
There are 2 issues that can cause these errors.
1) Messed up Partition table,
2) Broken eMMC chip (or more specifically, chip controller)
Issue 1 can be fixed by fixing the Partition table, which can be acheived by flashing an RUU.
Issue 2 cannot be fixed. (Unless you're a confident solder-er and know what you're doing, which chip to replace)
It is a hardware issue and your device will have to be returned.
Luckily, We don't know of anyone who has had an issue returning a rooted, s-off device.
There is more information in this thread, as well as how to know definatley whether you have the broken chip or not.
-Nipqer
Click to expand...
Click to collapse
The partition table is written specifically by Recovery, therefore flashing a new Recovery should write a new partition table. As for a hardware error? I doubt if the phone would boot properly after the third of fourth time if this were the case. A hardware problem causes software errors which spreads quickly like a virus, and because there's an error, the phone gets gunked up and cannot be fixed by a wipe.

What solved the issue? I have the same problem... (

If you have the broken chip, you'll have to return it and get it replaced under warranty.
-Nipqer

help my ds is brickt E:Can't open /cache/recovery/log

hello
my ds is in some kind of brick mode
for start i try to flash a saga rom with rom manager after im made s -off with revolution ... after i done that with success !?? my phone went block when installing apps and updates , after a few battery removes its blocks at the first screen
i try to restore from CMR v 3.0.2.6 but i have this massage
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
i can't restore or format
i try adb shell
mke2fs /dev/block/mmcblk0p27
but still nothing
pelease help

~ # mke2fs /dev/block/mmcblk0p27
mke2fs /dev/block/mmcblk0p27
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
76912 inodes, 307196 blocks
15359 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
38 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Warning: could not read block 0: Attempt to read block from filesystem resulted
in short read
Writing inode tables: done
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while
creating root dir
~ # reboot recovery
reboot recovery

I hate to be the bearer of bad news, but based on what I've read in other threads, and what you said, you may be dealing with faulty hardware now.
You say you pulled the battery. I'm sorry to say but pulling the battery seems Takea have a habit of frying the emmc chip in these phones and maybe others.
Have a look in this forum about broken emmc and broken emmc partitions and see if there's any suggestions there as to anything you can try. I would post a direct link to the thread here but I'm using the xda app and I have no idea how I would go out of this reply to retrieve a link. Sorry.
Post back here with what you find. I'm interested to know if it was what I think it is or not. I'm certainly no expert after all.
Sent from my HTC Desire S using XDA App

eddy ro said:
~ # mke2fs /dev/block/mmcblk0p27
mke2fs /dev/block/mmcblk0p27
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
76912 inodes, 307196 blocks
15359 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=67633152
38 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Warning: could not read block 0: Attempt to read block from filesystem resulted
in short read
Writing inode tables: done
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while
creating root dir
~ # reboot recovery
reboot recovery
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=1150917

i try moust off the http://forum.xda-developers.com/show....php?t=1150917 page
but i dont have the same errors , probabli because ai done a lot af adb sheell commands ... and i'm not a programer
i went to a a friend who has a mobile service
and he made me a service gold card and he sad i need a Shipped rom (i had )RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed = but not in exe or zip i ned o img file
so were can a find a img file whit the RUU_Saga_HTC_Europe_1.47.401.4 or a service rom
is other ways to do repair with the gold card

eddy ro said:
i try moust off the http://forum.xda-developers.com/show....php?t=1150917 page
but i dont have the same errors , probabli because ai done a lot af adb sheell commands ... and i'm not a programer
i went to a a friend who has a mobile service
and he made me a service gold card and he sad i need a Shipped rom (i had )RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed = but not in exe or zip i ned o img file
so were can a find a img file whit the RUU_Saga_HTC_Europe_1.47.401.4 or a service rom
is other ways to do repair with the gold card
Click to expand...
Click to collapse
I believe that if you run part the actual RUU exe that you need to install....just before it actually applies the update to the phone, it extracts its full contents to a local directory on the pc that you're using, you should be able to get these files from this temp directory after cancelling it.
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1002506&v=1&libid=1313147594477&out=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc7ce46%2Fn%2FRUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.exe&ref=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1146601&title=%5BROM%5DShipped%20Desire%20S%20ROM%20Collection%20-%20xda-developers&txt=http%3A%2F%2Fwww.filefactory.com%2Ffile%2Fcc7c...410_signed.exe&jsonp=vglnk_jsonp_13131477129241
Not 100% sure which directory though, sorry...perhaps google some more...or someone else will be able to help with this.

to the service whith the brick
after some different tries and a holiday break i had a live chat with htc , but they don't have answers when you instal custom rooms (i was very honest whit them)
they sad i must take the phone to service , lucky for me they have a service partner in my town (cluj-napoca , Romaina ) (i will meet face to face whit them) , so i will try to get more information as possible about this fault to keep all of us who have the same problem inform t.

CWM won't restore image

When trying to restore a backup image in CWM recovery i get an error. log shows the following:
Code:
Error while restoring /system!
block groups: 12
reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
unable to copy file ./app/accuweatherdaemon.apk
system
lost+found
app
accuweatherdaemon.apk
error while restoring /system!
I:Can't partition non-vfat: datamedia
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /emmc
phone won't boot now, trying to avoid having to download an image and flash via odin.
any help is much appreciated!

rocktonic said:
When trying to restore a backup image in CWM recovery i get an error. log shows the following:
Code:
Error while restoring /system!
block groups: 12
reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
unable to copy file ./app/accuweatherdaemon.apk
system
lost+found
app
accuweatherdaemon.apk
error while restoring /system!
I:Can't partition non-vfat: datamedia
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /emmc
phone won't boot now, trying to avoid having to download an image and flash via odin.
any help is much appreciated!
Click to expand...
Click to collapse
could this be because the backup is on an external SD card? if so, is there any way to move it without being able to boot?

[Q] Spontaneously /data and /cache unable to mount

Hi people, we really appreciate all you do for us. I have a question. I have a first seen problem here. Many of us have faced the /data cannot mount problem. HOWEVER I am in a slightly worst position. The reason is that I had corrupted /Data AND /Cache. I know that this thread http://forum.xda-developers.com/showthread.php?t=2683787 is ALMOST the same but trust me, everything I do is not enough as this thread is about the first part of my problem.
I own an HTC Sensation, I use TWRP ver 2.8.6, unlocked, S-off, Firmware 3.33, HBOT-1.27.1100, RADIO-11.24A.3504.31_M, OpenADSP-v05.6.0.2226.00.0418 and I use my pc terminal.
Accidentaly the battery dropped out while I was trying to clear Dalvik and cache to flash a new ROM as my last one was a bit heavy for me.
I have already tried this (with this difference "mmcblk0p23" ):
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p23
reboot
with this result:
~ # ←[6nmake_ext4fs /dev/block/mmcblk0p23
make_ext4fs /dev/block/mmcblk0p23
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: 79
Created filesystem with 11/76480 inodes and 10067/305852 blocks
But after that, (because I already had my ROM deleted) I cant proceed as any ROM I try to flash gives me an Error at /cache.
I mount manually /data through the recovery and that's all... Everything stucks at /cache...
I even tried that just in case:
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p23
which practically (I think) gives me the same result. However when I try to:
mount /data
mkdir -p /data/media/0
exit
adb push myrom.zip /data/media/0
nothing happens as it says I do not have the permission to write (its read-only and I don't know how to fix the permissions)
Sorry for the length but I already read all the thread and (as you can understand) my problem remains... Any help would be appreciated!
I just noticed that /SD-Ext and System too are not Mounted. The only 2 mounted options in my TWRP are sdcard and Data (which I manually mounted as I described above).
I can manually tick on System too when I do all this stuff I mentioned. However, if I try to tick /cache too, EVERYTHING roll back and I can't tick Data either...

Successfully flashed a ROM but stuck on HTC Logo

i know there are a lot of threads out there having the same problem as mine, but i think my situation is different, so need help on this.
Here it goes:
After i flashed my unlocked S-On HTC Sensation 4G T-Mobile back to Stock, i experienced wifi problem so i decided to flash again a rom compatible with my handset. After flashing Android_Revolution_HD-Sensation_1.2.2_T-Mobile, it's stuck on HTC Logo, so i decided to flash the Rom again. Now it can't seem to find my system and data partition, it says E: Format_volume: make_extf4fs failed. I solved the problem by partitioning my external sd card as system and data and installing another rom with the updater-script configured. Now the installer says it is sucessful but after i reboot, it's still stuck in the HTC logo. What should i do? I'm really desperate for help. Hope you can rescue me in this situation.
HEre is the installation Log (i have to delete the extract logs since it's too long):
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:11:37 1970
Preparing partitions
Formatting cache partition
unmount of /cache failed; no such volume
[Creating filesystem with parameters]:---
Size: 125784064
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 30709
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/7680 inodes and 1518/30709 blocks
warning: wipe_block_device: Discard failed
error: file_write: write: I/O error
E:make_ext4fs failed (1) on /dev/block/mmcblk0p24format: Can not format_ext4 emmc partition named "/dev/block/mmcblk0p24"ui_print
Installing system
Mounting system on sd-ext
about to run program [/sbin/busybox] with 6 args
Mounting Data on sd-ext2
about to run program [/sbin/busybox] with 6 args
Copying files
Setting permissions
Installing kernel
Copying kernel modules
Mounting /system on sd-ext
about to run program [/sbin/busybox] with 6 args
Extract: /system/lib/modules/bcmdhd.ko
Extract: /system/lib/modules/cdc-acm.ko
Extract: /system/lib/modules/option.ko
Extract: /system/lib/modules/pl2303.ko
Extract: /system/lib/modules/usb_wwan.ko
Writing boot image
Flashing Boot.img...
Kernel imaged flashed...
Finished
script result was [@Finished]
Installer Sucessfull (Status 0)
End at : Fri Jan 2 00:16:12 1970

did u flash boot.img after u flashed the rom?

jmcclue said:
did u flash boot.img after u flashed the rom?
Click to expand...
Click to collapse
no, how do i do that? if from fastboot, i don't think that's posible, adb can't detect my device.

iameg said:
no, how do i do that? if from fastboot, i don't think that's posible, adb can't detect my device.
Click to expand...
Click to collapse
adb & fastboot setup
http://www.google.ie/url?q=http://f...Z1GBjE&usg=AFQjCNG5wlDp1B-QvlsXu3HOD2a01TSDgw
plenty of guides here on xda for u to read if not sure of fastboot commands.
and u can always flash latest 4ext recovery and enable smart flash in settings, it flashes boot.img for s-on users.

HELP!
jmcclue said:
adb & fastboot setup
http://www.google.ie/url?q=http://f...Z1GBjE&usg=AFQjCNG5wlDp1B-QvlsXu3HOD2a01TSDgw
plenty of guides here on xda for u to read if not sure of fastboot commands.
and u can always flash latest 4ext recovery and enable smart flash in settings, it flashes boot.img for s-on users.
Click to expand...
Click to collapse
hi, after a few days of not having been able to attend to my htc sensation, now it doesn't charge (no led light indicator) and doesn't power on nor go to bootloader. how do i fix this? please help me.