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

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

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

Related

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.

[Q] Status 7 Error Pacman Rom

Hi I am constantly getting a status 7 error when trying to install the rom from here
here is the log from the recovery
any help would be greatly appreciated
Starting recovery on Thu Mar 14 14:13:44 2013
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Tue Feb 5 19:22:42 CET 2013
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT18NT202090
ro.baseband=26.17.14.11_M
ro.carrier=ATT
ro.bootloader=0.85.2007
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=70
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 12h-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 format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35760 inodes and 4484/142847 blocks
warning: wipe_block_device: Discard failed
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: 11/75200 files (0.0% non-contiguous), 13377/300799 blocks
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/76912 files (0.0% non-contiguous), 20002/307196 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
About to install:
saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Continue install?
-- Installing: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Finding update package...
I:Update location: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
E:Error in /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
(Status 7)
Installation aborted.
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 540.5MiB
data ext3 1.1GiB 1.0GiB
cache ext3 290.5MiB 265.5MiB
sdcard fat32 1.8GiB 924.3MiB
Current Rom: IceColdSandwich-8.2.AOKP
Start fixing permissions?
Fixing permissions...
/sbin/fix_permissions 2.04 started at 03-14-2013 10:15:20
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.04 ended at 03-14-2013 10:15:20 (Runtime:0m0s)
Done!
Could anyone tell me what I am doing wrong or help me correct this problem?
EDIT: I want to note that PAC-man-v20.0.1-BLINDNDUMB.zip installs without error its just the nightlies and PAC-man-v21.0.0-BLINDNDUMB.zip that do not work for me

thekool11 said:
Hi I am constantly getting a status 7 error when trying to install the rom from here
here is the log from the recovery
any help would be greatly appreciated
Starting recovery on Thu Mar 14 14:13:44 2013
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Tue Feb 5 19:22:42 CET 2013
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT18NT202090
ro.baseband=26.17.14.11_M
ro.carrier=ATT
ro.bootloader=0.85.2007
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=70
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 12h-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 format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35760 inodes and 4484/142847 blocks
warning: wipe_block_device: Discard failed
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: 11/75200 files (0.0% non-contiguous), 13377/300799 blocks
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/76912 files (0.0% non-contiguous), 20002/307196 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
About to install:
saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Continue install?
-- Installing: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Finding update package...
I:Update location: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
E:Error in /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
(Status 7)
Installation aborted.
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 540.5MiB
data ext3 1.1GiB 1.0GiB
cache ext3 290.5MiB 265.5MiB
sdcard fat32 1.8GiB 924.3MiB
Current Rom: IceColdSandwich-8.2.AOKP
Start fixing permissions?
Fixing permissions...
/sbin/fix_permissions 2.04 started at 03-14-2013 10:15:20
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.04 ended at 03-14-2013 10:15:20 (Runtime:0m0s)
Done!
Could anyone tell me what I am doing wrong or help me correct this problem?
EDIT: I want to note that PAC-man-v20.0.1-BLINDNDUMB.zip installs without error its just the nightlies and PAC-man-v21.0.0-BLINDNDUMB.zip that do not work for me
Click to expand...
Click to collapse
Have you checked md5sum?

glevitan said:
Have you checked md5sum?
Click to expand...
Click to collapse
Did you really need to quote all of that just to say that?
Sent from a dream.

I believe you're trying to flash a Saga ROM.

bananagranola said:
I believe you're trying to flash a Saga ROM.
Click to expand...
Click to collapse
I couldnt have been a bigger idiot, thank you very much lol this shouldve been obvious to me if I were paying attention the nightly I downloaded

thekool11 said:
I couldnt have been a bigger idiot, thank you very much lol this shouldve been obvious to me if I were paying attention the nightly I downloaded
Click to expand...
Click to collapse
Sorry noob here. I'm getting the status 7 error too and I have no clue what a saga rom is :/ how do i fix it?

A ROM for a different device: the Desire S, codenamed Saga. We are the forum for the Desire HD/Inspire 4G, codenamed Ace.

williamrazmy said:
Sorry noob here. I'm getting the status 7 error too and I have no clue what a saga rom is :/ how do i fix it?
Click to expand...
Click to collapse
here is a noob fiendly way to solve it
http://forum.xda-developers.com/showthread.php?t=2302599

[Q] bricked htc-corrupted partitions

Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>

noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
do you have access to the bootloader/recovery?

noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???

[email protected] said:
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
Click to expand...
Click to collapse
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo

noutsos said:
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
Click to expand...
Click to collapse
are you on S-ON?
post your bootloader details

rzr86 said:
are you on S-ON?
post your bootloader details
Click to expand...
Click to collapse
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M

noutsos said:
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
Click to expand...
Click to collapse
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?

rzr86 said:
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
Click to expand...
Click to collapse
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo

noutsos said:
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
Click to expand...
Click to collapse
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?

rzr86 said:
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
Click to expand...
Click to collapse
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted

noutsos said:
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
Click to expand...
Click to collapse
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?

rzr86 said:
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
Click to expand...
Click to collapse
tried ruu exe but nth happened,cant find the device,and cant fastboot

How does fastboot not work? Does usb not connect at all?

Hey guys, any news about fixing bug in TWRP which caused corrupting partitions and bricking phones?

Hi guys,
I have the same issue as OP, however only the /data won't get mounted. My phone got stuck while doing wipe of the data partition in TWRP 2.6.3.0 (it didn't freeze, but it was taking over 40 minutes already), so I had to take the battery out and put it back in.
First, I tried using TWRP 2.6.3.0 to perform the wipe again, but I got
Code:
E:Unable to mount '/data'
I got the same error when I tried to install any ROM, so the installation got aborted.
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'.
Here is my bootloader info:
S-OFF
Firmware 3.33
HBOOT 1.27.1100
Radio 11.24A.3504.31_M
I am pretty much desperate at this point. Is there any way or chance of fixing my partitions? I haven't tried fixing it using parted, because I was unable to find a good howto for Sensation. I would be happy for any advice.

MatesCZ said:
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'..
Click to expand...
Click to collapse
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom

rzr86 said:
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
Click to expand...
Click to collapse
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo

MatesCZ said:
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
Click to expand...
Click to collapse
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one

rzr86 said:
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
Click to expand...
Click to collapse
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
...
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Click to expand...
Click to collapse

MatesCZ said:
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Click to expand...
Click to collapse
yeah you are right
some partitions are broken probably from TWRP because a lot of users faced issues similar with yours
someone posted a solution few days ago how to boot a rom from sdcard
he had also broken partitions in internal memory caused from TWRP and he managed to boot a rom from sdcard
he created two partitions
one to be recognized as /data and one to be recognized as /system and mounted them successfully(if i remember well)
but i can't find that post
if i find it i will come with edit

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

[peregrine]System read-only, can't update TWRP, flash or wipe

Hi everyone, thanks for the awesome place that XDA is!
As the title suggests I'm into a bit of trouble with my XT1039! (Moto G 4G 2nd gen/peregrine)
I had previously been running AOSP Extended and then Lineage 14.1 by MSe1969 without too much issues for 1-2 years.
Every app started crashing on my phone, I rebooted thinking it was just a temporary issue.
When I realized it wouldn't boot again I set to flash a newer version of the Lineage ROM and here starts the fun.
I did a more-than-what's-necessary wipe to get rid of any serious issue, I didn't mind losing anything I had on the phone.
The zip install would then not work, log:
Code:
BLKDISCARD ioctl failed: I/O error
failed to execute command [erase 6,70603,97792,131586,163328,197122,228864]
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.
error: 1001
Updater process ended with ERROR: 7
Only after this first issue did I realize what really was wrong:
The wipe had not had any effect at all, even though not showing any error.
I tried updating TWRP to 3.5.9 using Install > Install images and then "fastboot flash" which also didn't show any error yet had no effect at all, I was back to 3.3.1 after that. The only way I just found to run TWRP 3.5.9 is with "fastboot boot twrp....img" though I don't think that makes the situation any different?
The whole system is locked on read-only and the various operations as well as dmesg show error on the internal mmcblk0 although not as bad as what I've seen on other threads. This looks similar: https://forum.xda-developers.com/t/my-xt1039-lte-is-soft-bricked-please-help.3595044/ although we don't get to see any log.
Log during wipe shows about 20k lines like this one, presumably one for every file despite resulting success:
Code:
I:Unable to unlink '/data/misc/bluedroid/bt_config.bak': Read-only file system
Relevant part of dmesg from boot:
Code:
<3>[ 44.781618,0] mmcblk0: error -110 transferring data, sector 2670487, nr 1, cmd response 0x900, card status 0x0
<3>[ 44.783137,0] end_request: I/O error, dev mmcblk0, sector 2670487
<2>[ 44.784164,0] EXT4-fs error (device mmcblk0p34): ext4_find_entry:941: inode #1759: comm recovery: reading directory lblock 0
<3>[ 44.784379,0] Aborting journal on device mmcblk0p34-8.
<2>[ 44.784988,0] EXT4-fs (mmcblk0p34): Remounting filesystem read-only
<2>[ 44.785980,0] EXT4-fs error (device mmcblk0p34): ext4_put_super:844: Couldn't clean up the journal
Output of mount command:
Code:
# mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=440132k,nr_inodes=110033,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)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=440132k,nr_inodes=110033)
/dev/block/mmcblk0p33 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p36 on /data type f2fs (ro,seclabel,relatime,background_gc=off,user_xattr,inline_xattr,acl,inline_data,active_logs=6)
/dev/block/mmcblk0p36 on /sdcard type f2fs (ro,seclabel,relatime,background_gc=off,user_xattr,inline_xattr,acl,inline_data,active_logs=6)
/dev/block/mmcblk1p1 on /sdcard1 type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Log for "Format data" operation which I also tried several times:
Code:
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.4.42-g5e5969d-dirty ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Feb 7 22:11:19 CET 2016"
Error: Could not conduct fsync!!!
Info: format successful
I:mkfs.f2fs -t 0 /dev/block/mmcblk0p36 process ended with RC=0
Done.
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
You may need to reboot recovery to be able to use /data again.
Updating partition details...
I:Data backup size is 3927MB, free: 1191MB.
This would be enough indications to declare the internal ROM dead if I could have at least found one other thread with the same issue, and it doesn't look as bad as what I've seen during my search.
Googling has resulted in extremely few results for the specific errors reported (Could not conduct fsync or BLKDISCARD for example) as they are either non-android specific or very rare.
Would it be worth it to try to flash from fastboot?
I've seen it advised here and there, I'd be more than happy if I could be pointed to useful documentation on the process.

Database Info

welcome