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

opumps · Jul 2, 2011

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.

"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://xdaforums.com/showpost.php?p=16135893&postcount=27

A eMMC design flaw, Confirming info from htc-offical (thanks apairofscissors)
http://xdaforums.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].

ben_pyett · Jul 2, 2011

Not identical but market related to this thread http://xdaforums.com/showthread.php?t=1141843

Sent from my HTC Desire S using XDA Premium App

zorbakun · Jul 2, 2011

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...

opumps · Jul 2, 2011

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...

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)

zorbakun · Jul 2, 2011

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.

InfernalByte · Jul 2, 2011

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

opumps · Jul 2, 2011

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.

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)

zorbakun · Jul 2, 2011

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.

opumps · Jul 2, 2011

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!

Numline1 · Jul 2, 2011

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???).

opumps · Jul 2, 2011

Numline1 said:
(how can market or battery pulled out brick phone???.

indeed!!!!

szallah · Jul 3, 2011

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...

opumps · Jul 4, 2011

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...

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.

shrome99 · Jul 24, 2011

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

InfernalByte · Jul 24, 2011

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.

shrome99 · Jul 24, 2011

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?

Nipqer · Jul 24, 2011

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

InfernalByte · Jul 24, 2011

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

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.

dbezzegh · Jul 27, 2011

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

(

Nipqer · Jul 27, 2011

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

-Nipqer

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

Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Similar threads

Top Liked Posts