[HTC Desire S] somerandomhash:
Fried eMMC Chip?

Revolution

----------

SAGA PVT SHIP S-OFF RL

HBOOT-6.98.1002

RADIO-3805.06.02.03.M

eMMC -boot

Mar 10 2011 14.58.38

Ok, I have been pulling my hair (& teeth) out with this all nite. I appear to have a fried chip (as verified by info in the INDEX THREAD)

I have tried rolling back the HBOOT (enghboot_0.98.2000/enghboot_0.98.000/engHBOOToverARX) via various methods (always get either 'cannot roll back hboot' or freeze.)

Further investigation leads me to conclude revolution is 'locked' from downgrades. I read as much as I could find and followed amidabuddha instructions here

C:\Users\Downloads\FlashENGHBOOT>fastboot flash hboot hboot.img
sending 'hboot' (1024 KB)... OKAY
writing 'hboot'... INFOimage update is bypassed!
OKAY

C:\Users\Downloads\FlashENGHBOOT>fastboot reboot-bootloader
rebooting into bootloader... FAILED (status read failed (Too many links))

I have been able use QtADB (0.8.1) and the phone connects briefly and then seems to disconnect. I have access to CWM.

As I understand it I am not going to get a warranty repair (which is seriously unfair as this seems to be a hardware issue) others have tried and failed.

I have tried to flash the coresponding RUU (RUU_Saga_H3G_UK_1.31.771.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178937_signed) but am stuck at the 'Rebooting to Bootloader' stage.

Update:

Followed the thread and found http://wp.daveheavyindustries.com/2011/09/13/htc-desire-s-flashing-problems-m4g2de/

Strangely I also get:

~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 8.284240] mmc0: No card detect facilities available
<6>[ 8.284881] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.285034] mmc0: Platform slot type: MMC
<6>[ 8.285247] mmc0: 4 bit data mode disabled
<6>[ 8.285369] mmc0: 8 bit data mode enabled
<6>[ 8.285522] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.285766] mmc0: Slot eject status = 0
<6>[ 8.285888] mmc0: Power save feature enable = 1
<6>[ 8.286132] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2c1000
<6>[ 8.286254] mmc0: DM cmd busaddr 0x0c2c1000, cmdptr busaddr 0x0c2c1300
<6>[ 8.439575] mmc0: new high speed MMC card at address 0001
<6>[ 8.440795] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

~ # mke2fs -j /dev/block/mmcblk0p27
mke2fs -j /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

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

Which seems to be a good thing, HOWEVER when I try the next command:

~ # e2fsck /dev/block/mmcblk0p27
e2fsck /dev/block/mmcblk0p27
e2fsck 1.41.6 (30-May-2009)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab
file while determining whether /dev/block/mmcblk0p27 is mounted.
e2fsck: Attempt to read block from filesystem resulted in short read while tryin
g to open /dev/block/mmcblk0p27
Could this be a zero-length partition?

UPDATE 2

I have tried to do what I understand is the DD method (I have root via adb) but get a no such file, despite the fact it is there...

~ # dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.059481 seconds, 16.8MB/s
~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd: can't open '/sdcard/hboot.img': No such file or directory

UPDATE 3

I tried http://xdaforums.com/showpost.php?p=18051062&postcount=2

C:\Users\Downloads\AndroidFlasher\Data>fastboot flash hboot hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.182s]
writing 'hboot'...

Which just hangs, so despite the fact my emmc

dmesg | grep mmc0

suggests no problem there obviously is.

UPDATE: Probably the wrong thread to be noticed but I did some stuff with the helpful guhl99 and some of the other knowing guys at #G2ROOT on freenode irc

We have pretty much established that it is a fried emmc chip, so it's going back to HTC for a warranty repair.

SOFF is irrelevant here as this is a known manufacturing fault which put's them in breach of the UK's Sale of Goods Act 1979