@somerandomhash: I've been living in the UK for a month, so I'd like to ask you, how do I pursue such a claim?
You would be writing a letter notifying the claim and then pursuing it, it depends on a few factors.
@somerandomhash: I've been living in the UK for a month, so I'd like to ask you, how do I pursue such a claim?
You would be writing a letter notifying the claim and then pursuing it, it depends on a few factors.
well HTC were no help
sent off the phone for repaire and got it back stating it had illegal software on it
so no fix under warranty.
anyone got anymore suggestions?
or where i can get the eMMC replaced in the UK and how much it would cost?
cheers
good question!
now, here is how you would like to be sure:
through
check your eMMC good or badCode:dmesg | grep mmc0
(http://xdaforums.com/showpost.php?p=13895268&;postcount=48)
my bad eMMC showed:
Code:<6>[ 7.724700] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2b3000 <6>[ 7.724822] mmc0: DM cmd busaddr 0x0c2b3000, cmdptr busaddr 0x0c2b3300 <6>[ 7.878082] mmc0: new high speed MMC card at address 0001 <6>[ 7.879425] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB (the bad one ----SAMSUNG104, KLM4G2DEJE A001, FDAE15PC. check the pics on the 1st post) [COLOR="Red"]===error info continued===[/COLOR] <3>[ 9.058532] mmc0: [COLOR="red"]Failed[/COLOR] to get card ready i = 123225 <6>[ 9.058654] mmc0: reinit card <4>[ 9.058746] mmc0: Starting deferred resume <6>[ 11.100524] mmc0: Deferred resume [COLOR="red"]failed[/COLOR] <3>[ 11.245941] mmc0: DMA channel flushed (0x80000004) <6>[ 11.246276] mmc0: Controller has been reset <6>[ 11.246459] mmc0: Worked around bug 1535304 <3>[ 11.247863] mmc0: DMA channel flushed (0x80000004) <6>[ 11.248229] mmc0: Controller has been reset <6>[ 11.248474] mmc0: Worked around bug 1535304 <6>[ 11.255096] mmc0: reinit card <4>[ 11.255187] mmc0: Starting deferred resume <6>[ 13.292724] mmc0: Deferred resume [COLOR="red"]failed[/COLOR]
and, here came the new one, the Sandisk eMMC 4GB
Code:<6>[ 8.538543] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c3f7000 <6>[ 8.538696] mmc0: DM cmd busaddr 0x0c3f7000, cmdptr busaddr 0x0c3f7300 <6>[ 8.692291] mmc0: new high speed MMC card at address 0001 <6>[ 8.693878] mmcblk0: mmc0:0001 SEM04G 3.68 GiB (new Sandisk's) [COLOR="navy"]===END no more error===[/COLOR]
t's probably a bit late for you but it might help others : whePreviously when i face the same problem, event running the stock RUU update from fastboot doesn't help. It hang halfway.
You dont need to buy that part. Try this guide: http://xdaforums.com/showthread.php?t=1575272
So this guide won't work on desire s ( with fried emmc ) or your desire s is not working now because of riff ?
hi again..
i dont know this guide is working or not..it is customer's desire s and i really dont know the phone history.. jtag pins r broken but it is repairable with usb cable but eMMC totally dead..
U can try this: http://xdaforums.com/showthread.php?t=1756287
Sent from my fried HTC Desire S using xda app-developers app
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
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
Formating /cache...
Cache wipe complete.
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
-Checking Model ID
-success!
-Model ID - HTC sage
Now flashing
E:Error in /sdcard/*******.zip
(Status 1)
Installation aborted.
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
rebooting bootloader ......
upgrading ROM image in your Android Phone...
Please do NOT disconnect USB cable nor run any program.
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]
HBOOT
[INDENT]Parsing...[SD ZIP]
[1] RECOVERY -updating
*********
Updating is in progress...
Do not power off the device!
[/INDENT]
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]
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)
/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]
~ # 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]
~ # 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]
~ # 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]
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].