yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] Meari:
Hi.

Today my desire s went crazy too.=)

So, symptoms are:

-after switching on stops on htc logo screen

-doesn't hard reset

-doesn't recovery

I tried your tutorial, but PC cannot see the phone even with adb.

Phone is not branded, h-boot ver. 0.98.0002.

Thanks for help.
[HTC Desire S] amidabuddha:
I assume that it is not S-OFF as well (or you have used xtc, maybe) so you case is slightly different

First: make sure that your adb/fasboot setup is correct (check the link in my signature)

Reboot to bootloader (hold Volume down, press Power, do not let Volume down go, release power button)

Connect to PC, make sure it is written FASTBOOT USB on the phone screen.

open cmd and type

fastboot devices

your device serial number has to be displayed. Then

fastboot erase cache
fastboot reboot

wait (if this worked after about 10 minutes you will see your lockscreen)

If this is not working download RUU that corresponds to your region from here

Reboot to bootloader (as described above in FASTBOOT USB mode) and start RUU.exe on your PC
[HTC Desire S] siimmaivel:
I did the full format in FAT32 with the default allocation unit size. The

ls /dev/block/

command returned the same table as before. In other words mmcblk1p1 did not appear in the list. When I try to mount SD card again, I recieve an answer that the mounting was failed because there is no mmcblk1p1.
[HTC Desire S] amidabuddha:
Your sdcard is there do not worry. The command "mount /sdcard" did the trick. I said "or" remember? :)

Can you see my last reply to you please?
[HTC Desire S] siimmaivel:
I tried to recieve the backup.img again, but it did not work this time. The output of the parted guide is:

C:\Windows\system32>adb shell
~ # parted /dev/block/mmcblk1
parted /dev/block/mmcblk1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: SD SD16G (sd/mmc)
Disk /dev/block/mmcblk1: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number Start End Size File system Flags
1 0.00B 16.0GB 16.0GB fat32

(parted)

I also tried to Is /dev/block/ command again to see if the mmcblk1 had been parted, but the table looked the same.

---------- Post added at 09:58 PM ---------- Previous post was at 09:51 PM ----------

My bootloader is still 6.98.1002 and I managed to capture the backup.img file, but its size is 0 bytes. I cannot even upload it anywhere.
[HTC Desire S] amidabuddha:
When you type the commands fastboot flash hboot.img make sure that the file hboot.img is in the same folder that the cmd path says. For example C:\android-tools
[HTC Desire S] Meari:
Thanks a lot for your help, but both way didn't work.

It just stucked for more then 30 min without any changes.=(
[HTC Desire S] siimmaivel:
I revieved the same result as before:

C:\Users\E6410>adb shell
~ # mount /sdcard
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory
~ # dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd: /dev/block/mmcblk0p18: I/O error
~ # 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
~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd: writing '/dev/block/mmcblk0p18': I/O error
1+0 records in
0+0 records out
0 bytes (0B) copied, 4.734085 seconds, 0B/s
~ #

As the XDA does not allow to upload .img, I made it into .rar and added the backup.img file there.
[HTC Desire S] amidabuddha:
Any errors or messages?
[HTC Desire S] amidabuddha:
Thanks. Check my previous post also (I edited it)

Also you can try the following:

Extract userdata, boot and system system images from rom.zip and flash them one by one with fastboot, like: fastboot (name) (name).img
[HTC Desire S] Meari:
Nope. On the phone screen is a fastboot menu, on the PC "erasing cash" or "directing to loader(I'm not sure about this word in english, but I hope u know what i mean)".
[HTC Desire S] amidabuddha:
Is you phone s-off? If not go to revlutionary.io and follow the instructions
[HTC Desire S] spankranger:
Sorry to post this now instead of before.

But i now have acces to fastboot and tried the code with this result:

C:\android-tools>fastboot devices

HT13KTJ3xxxx fastboot

C:\android-tools>fastboot oem h

...

(bootloader) command list

(bootloader) keytest

(bootloader) heap

(bootloader) boot

(bootloader) reset

(bootloader) powerdown

(bootloader) rebootRUU

(bootloader) heap_test

(bootloader) rtask

(bootloader) task

(bootloader) enableqxdm

(bootloader) gencheckpt

(bootloader) list_partition_emmc

(bootloader) load_emmc

(bootloader) check_emmc

(bootloader) check_emmc_mid

(bootloader) read_mmc

(bootloader) get_wp_info_emmc

(bootloader) send_wp_info_emmc

(bootloader) get_ext_csd_emmc

(bootloader) get_sector_info_emmc

OKAY [ 0.049s]

finished. total time: 0.066s

The output of sdparted:

copyright information of GNU Parted

(parted) print

print

print

Model: SD SU08G (sd/mmc)

Disk /dev/block/mmcblk1: 7948MB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Number Start End Size Type File system Flags

1 4194kB 7948MB 7944MB primary fat32

(parted)

Is this a good thing?
[HTC Desire S] Meari:
Thank you for help.

My phone is s-on. I followed all the instructions on revlutionary.io, but it stucks in "waiting for device". It's so weird, cause the device serial is shown in "fastboot devices" and it's also in "android usb devices" in device manager.
[HTC Desire S] siimmaivel:
I tried doing that. It failed to flash any of these files. However, when I changed the hboot_0.98.0000_361a7ba6_0310.img to hboot.img, it was successful, but the hboot version in bootloader did not change and the bootloader said that "you cannot downgrade hboot" or something like that. I tried flashing other .img's as well and radio.img started flashing, but it did not finish writing (it frose for 20 mins or so). Also system.img started flashing, but after 30 mins it was still nothing.

I'm leaving the system.img to flash for the night, but I don't have my hopes high.

But still thank you for your assistance! If you come up with anything else I could do, even how to successfully brick my phone for warranty then keep me posted. Thanks and good night!
[HTC Desire S] amidabuddha:
If it s-on do not bother to fix it yourself, go straight for a warranty repair!

Or you can try to reinstall the HTC drivers and try the both again.

Do not worry your sdcard is fine...(this is what you have checked with the parted command).

Try to overwrite your hboot from adb shell with the 'dd' command. Actually you can try everything that is posted here since your last post.

Can you copy the output of commands:

fastboot oem list_partition_emmc
fastboot oem load_emmc
fastboot oem check_emmc
fastboot oem check_emmc_mid
fastboot oem read_mmc
fastboot oem get_wp_info_emmc
fastboot oem get_sector_info_emmc

adb shell dmesg

Yse Pastebin and post the links here...Also tell me what was the result if you tried the commands "parted /dev/block/emmcblk0pxx mkfs 1 ext3"?

in adb shell type the following:

dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img

attach the file here

aslo the output of

adb shell dmesg

Also tell me what was the result if you tried the commands "parted /dev/block/emmcblk0pxx mkfs 1 ext3"?
[HTC Desire S] fbcyborg:
Again... this is because of two possible reasons:

1) you partitioned and formatted the SD Card, but it has been corrupted and cannot be seen by your device.

2) you have not partitioned and formatted your SD card.

I guess you are in case 2.

So, consider to download SystemRescueCd and let it boot until the shell has come. Then type startx and wait for the graphical interface.

Insert your SD Card into the PC using an SD card reader(1).

Then go into the menu, search and launch gParted. Then select the device, in the upper right corner of the application, which is recognized to be the SD Card (

be sure this is not your hard drive

!!!).

Then partition the SD Card and set it as FAT partition.

Finally, close the gparted application and in the shell type:

mkfs.vfat /dev/sd*1

Substitute the "*" with the right letter which has been associated to the SD Card.

(1)NB: to be sure what is the /dev/sd* associated to the SD card you can:

1) Open the Shell (it should be already opened)

2) type: tail -0f /var/log/messages

3) insert the SD Card

4) read what is being printed out

You should see something like /dev/sd**

Now, inserting the sdcard again into the phone you should see /dev/block/mmcblk1p1

Hope this helps.
[HTC Desire S] amidabuddha:
Ok:

1) Since his SDcard is mountable (he can start PG88IMG.zip from it as well as write the backup.img [that is empty by another reason]) and the parted command shows that he has a partition under mmcblk1 (the other case but it is similar), with a proper start, end and size, not aligned but this is not a great problem.

2) and he has an Input/Output error on his hboot partition (dd: /dev/block/mmcblk0p18: I/O error) not on the SDcard.

What is the importance of messing with it?

It is better to focus on bricking/fixing the device itself...
[HTC Desire S] fbcyborg:
Ok ok... you are certainly right.

I suggested to do in that way to ensure the partition has been created.
[HTC Desire S] Meari:
Thank you very much for your time & for your help.
[HTC Desire S] amidabuddha:
:) xx are the numbers. This was related to my post here. What was the result of this procedure

especially this one:

parted /dev/block/mmcblk0p27 mkfs 1 ext3

also it seems that your dmsg log is not starting from the beginning. Do this:

adb shell dmesg > /sdcard/dmesg

attach the file here
[HTC Desire S] amidabuddha:
try the following:

adb shell
mount -a
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img
[HTC Desire S] siimmaivel:
The result:

C:\Users\E6410>adb shell
~ # mount -a
mount -a
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or director
y
~ # dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img
dd: /dev/block/mmcblk0p17: I/O error
[HTC Desire S] amidabuddha:
see my previous post also
[HTC Desire S] siimmaivel:
I added the file to .rar container in the attachments.
[HTC Desire S] siimmaivel:
C:\Users\E6410>cd C:\sdparted

C:\sdparted>adb push e2fsck /sbin/
1677 KB/s (428664 bytes in 0.249s)

C:\sdparted>adb push mke2fs /sbin/
960 KB/s (30680 bytes in 0.031s)

C:\sdparted>adb push parted /sbin/
1550 KB/s (346680 bytes in 0.218s)

C:\sdparted>adb push resize2fs /sbin/
1396 KB/s (22304 bytes in 0.015s)

C:\sdparted>adb push sdparted /sbin/
502 KB/s (16047 bytes in 0.031s)

C:\sdparted>adb push tune2fs /sbin/
466 KB/s (22364 bytes in 0.046s)

C:\sdparted>adb shell
~ # cd /sbin
cd /sbin
/sbin # chmod 0755 e2fsck
chmod 0755 e2fsck
/sbin # chmod 0755 mke2fs
chmod 0755 mke2fs
/sbin # chmod 0755 parted
chmod 0755 parted
/sbin # chmod 0755 resize2fs
chmod 0755 resize2fs
/sbin # chmod 0755 sdparted
chmod 0755 sdparted
/sbin # chmod 0755 tune2fs
chmod 0755 tune2fs
/sbin # parted /dev/block/mmcblk0p25 mkfs 1 ext3
parted /dev/block/mmcblk0p25 mkfs 1 ext3
parted /dev/block/mmcblk0p26 mkfs 1 ext3
parted /dev/block/mmcblk0p26 mkfs 1 ext3
parted /dev/block/mmcblk0p27 mkfs 1 ext3
parted /dev/block/mmcblk0p27 mkfs 1 ext3
[HTC Desire S] amidabuddha:
no errors! try now RUU while in FASBOOT USB
[HTC Desire S] siimmaivel:
I'm going to try it out in 3h. Thanks!
[HTC Desire S] siimmaivel:
RUU is still stuck at "Rebooting to Bootloader..." screen for an half an hour... The same as before.
[HTC Desire S] Skanob:
Possible FIX for the infamous eMMC problem..
[HTC Desire S] amidabuddha:
Lets try a different approach.

From adb shell type the following:

cat /dev/block/mmcblk0p17 > /sdcard/misc.img
cat /dev/block/mmcblk0p18 > /sdcard/hboot.img

if this works without an I/O error attach the both files here
[HTC Desire S] siimmaivel:
Unfortunately, still the same error:

C:\Users\E6410>adb shell
~ # cat /dev/block/mmcblk0p17 > /sdcard/misc.img
cat /dev/block/mmcblk0p17 > /sdcard/misc.img
cat: read error: I/O error
~ # cat /dev/block/mmcblk0p18 > /sdcard/hboot.img
cat /dev/block/mmcblk0p18 > /sdcard/hboot.img
cat: read error: I/O error

Could it be just that the internal memory is somewhat physically damaged?
[HTC Desire S] amidabuddha:
I have made some reading and there is a lot of info on the other forums about bad blocks on your internal memory. Also I compared your dmesg with mine and it seems that your memory is less than mine (and we are running the same devices, with the same chip). If this is the case it cannot be solved with any software methods. The chip has to be replaced. But there is a chance that your partition table is messed up and the system cannot find the proper mount locations.
[HTC Desire S] amidabuddha:
I really hope that you will make this is adb shell:

cat /dev/block/mmcblk0 > /sdcard/mmc.img

if no error this will take some time (the file will be about 2 GB) but if I can get that file there is a big chance of positive outcome
[HTC Desire S] amidabuddha:
Put aside all that I was suggesting so far. Try the command from my previous post and if it works there is big chance that we will fix your problem
[HTC Desire S] spankranger:
The output of the fastboot oem commands

http://pastebin.com/8SG8t6k6

The output of: adb shell dmesg

http://pastebin.com/4czerRG9

I also tried the "total brick or new bootloader" method.

fastboot erase hboot

fastboot flash hboot hboot.img

fastboot reboot bootloader

And got almost the same output as siimmaivel.

result: http://pastebin.com/KRQb4hDt

I tried "fastboot boot hboot.img"

http://pastebin.com/Y2tu6kZ0

"fastboot oem rebootRUU"

The phone freezes and the cursor keeps blinking for an hour in cmd.

I also have tried to re-instal the nandroid backup (from my sdcard)

In the restore menu of ClockworkMod Recovery v5.0.2.0, but each time it gives me the folowing result:

Checking MD5 sums...

Erasing boot before restore...

Restoring boot image...

Restoring system...

then out of nothing it stops and the menu of clockworkmod apears again.

I seems like nothing changed.

The last thing i tried todat was to overwrite my hboot from adb shell with the 'dd' commands.

dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img

dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18

1. i put the hboot.img in the root of the sdcard.

2. In cmd enter the following commands:

adb devices

adb shell

su (here it goes wrong) it says:

C:\android-tools>adb shell

~ # su

su

/sbin/sh: su: not found

What can this mean?

I have the su file in the C:\android-tools map
[HTC Desire S] amidabuddha:
Thank you for the info. I can see that your case is absolutely identical with that of siimmaivel. The "#" symbol means that you are root already and you do not need su command. It seems that by some reason your partitions are of out their mount points. Can you make the command in my post above (No96)? If this works attach the file somewhere and paste the link. I really hope that this will work because this is the last thing that comes in mind to do...and it has a great chance of success
[HTC Desire S] siimmaivel:
I tried some combinations of the past suggestions and as it seems there is a problem of mounting mmcblk0p25, mmcblk0p26 and mmcblk1p1 on SD card:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>adb shell
~ # mount -a
mount -a
cat /dev/block/mmcblk0 > /sdcard/mmc.img
cat /dev/block/mmcblk0 > /sdcard/mmc.img
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or director
y
~ # cat /dev/block/mmcblk0 > /sdcard/mmc.img
cat: read error: I/O error
~ # cat /dev/block/mmcblk0 > /sdcard/mmc.img
cat /dev/block/mmcblk0 > /sdcard/mmc.img
cat: read error: I/O error
~ # mount -a
mount -a
cat /dev/block/mmcblk0 > /sdcard/mmc.img
cat /dev/block/mmcblk0 > /sdcard/mmc.img
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p25 on /system failed: Invalid argument
~ # cat /dev/block/mmcblk0 > /sdcard/mmc.img
cat: read error: I/O error
~ # mount /sdcard
mount /sdcard
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or director
y
~ #

Also, I tried formating everythin again: cache, data, delvik cache, battery status, system and sdcard. Format was successful in all cases exept when I tried to flash /system. Then I got: "Error formating /system!" I don't know if this is of any help...
[HTC Desire S] spankranger:
I'm almost losing my last hope.. this also did not work.

C:\android-tools>adb shell

~ # cat /dev/block/mmcblk0 > /sdcard/mmc.img

cat /dev/block/mmcblk0 > /sdcard/mmc.img

cat: read error: I/O error

~ #

Thanks again for your time and help amidabuddha.
[HTC Desire S] amidabuddha:
Ok. Lets go to parted again. Paste here the output of:

parted /dev/block/mmcblk0p17
print
parted /dev/block/mmcblk0p18
print
parted /dev/block/mmcblk0p25
print
parted /dev/block/mmcblk0p26
print
parted /dev/block/mmcblk1p1
print

I have a strange feeling that we are circling around the solution

Also if you noticed there is no longer a problem with mounting the /cache - mmcblk0p27!
[HTC Desire S] spankranger:
I have noticed that there's also a problem with mmcblk0p27

~ # parted /dev/block/mmcblk0p27

parted /dev/block/mmcblk0p27

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0p27

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

print

Error: /dev/block/mmcblk0p27: unrecognised disk label

(parted)

The output of parted:

~ # parted /dev/block/mmcblk0p17

parted /dev/block/mmcblk0p17

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0p17

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

print

Error: /dev/block/mmcblk0p17: unrecognised disk label

(parted)

~ # parted /dev/block/mmcblk0p18

parted /dev/block/mmcblk0p18

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0p18

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

print

Error: /dev/block/mmcblk0p18: unrecognised disk label

(parted)

~ # parted /dev/block/mmcblk0p25

parted /dev/block/mmcblk0p25

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0p25

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

print

Error: /dev/block/mmcblk0p25: unrecognised disk label

(parted)

~ # parted /dev/block/mmcblk0p26

parted /dev/block/mmcblk0p26

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0p26

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

print

Error: /dev/block/mmcblk0p26: unrecognised disk label

(parted)

~ # parted /dev/block/mmcblk1p1

parted /dev/block/mmcblk1p1

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk1p1

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

print

Model: Unknown (unknown)

Disk /dev/block/mmcblk1p1: 7944MB

Sector size (logical/physical): 512B/512B

Partition Table: loop

Number Start End Size File system Flags

1 0.00B 7944MB 7944MB fat32

(parted)

BTW i get some new hope by reading this guide: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/

The only problem is that it's written for another phone, still i think it can work for the Desire S too... or not?
[HTC Desire S] amidabuddha:
From the log I can see that you are doing this too fast.

Type "parted /dev/block/mmcblk0p26" and wait. When the message "Welcome to GNU Parted!" should appear. Then you type "print" and copy the output.

Then better type "quit" and do this again for the other partitions (27, 1p1,...)

The output shoul be something like this:

~ # parted /dev/block/mmcblk1
parted /dev/block/mmcblk1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: SD SD16G (sd/mmc)
Disk /dev/block/mmcblk1: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: loop

Number Start End Size File system Flags
1 0.00B 16.0GB 16.0GB fat32

(parted)
[HTC Desire S] siimmaivel:
I did it more carefully this time, but still no good results:

C:\Users\E6410>adb shell
~ # parted /dev/block/mmcblk0p17
parted /dev/block/mmcblk0p17
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p17
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: /dev/block/mmcblk0p17: unrecognised disk label
(parted) quit
quit
quit
~ # parted /dev/block/mmcblk0p18
parted /dev/block/mmcblk0p18
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p18
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: /dev/block/mmcblk0p18: unrecognised disk label
(parted) quit
quit
quit
~ # parted /dev/block/mmcblk0p25
parted /dev/block/mmcblk0p25
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p25
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: /dev/block/mmcblk0p25: unrecognised disk label
(parted) quit
quit
quit
~ # parted /dev/block/mmcblk0p26
parted /dev/block/mmcblk0p26
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p26
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: /dev/block/mmcblk0p26: unrecognised disk label
(parted) quit
quit
quit
~ # parted /dev/block/mmcblk1p1
parted /dev/block/mmcblk1p1
Error: Could not stat device /dev/block/mmcblk1p1 - No such file or directory.
Retry/Cancel? Retry
Retry
Retry
Error: Could not stat device /dev/block/mmcblk1p1 - No such file or directory.
Retry/Cancel?
[HTC Desire S] amidabuddha:
So your partitions are not ext3 even after the formatting.

You can try to format the SDcard from recovery and then check do you have the mmcblk1p1 partition with

ls /dev/block

in adb shell

If this not working do this:

Make a Goldcard - this will erase all the data on your SDcard, so make a backup first (check the tool here). The Goldcard should allow to your system to skip all the verification and checks and flash whatever you want. After your Goldcard is ready, put it into your device and copy the PG88IMG.zip (the renamed rom.zip from the RUU) on it. Then reboot to bootloader, go to hboot and confirm the update.
[HTC Desire S] spankranger:
I have edited my post # 103

Now i have found the problems with parted en post them.
[HTC Desire S] amidabuddha:
Yes but it seems that you have no problem with the mounting of the SDcard at least. Try the Goldcard solution from my previous post
[HTC Desire S] amidabuddha:
Another check that can give some more info (or confirm that bad blocks theory) should be:

umount /dev/block/mmcblk0p26

if it gives error like this: umount device or resource busy do

umount -l /dev/block/mmcblk0p26

then:

e2fsck -y -v -f /dev/block/mmcblk0p26

you can do the same on mmcblk0p25 and mmcblk0p27

also do:

mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27

if no errors

upgrade_fs

Btw have you tried the 4EXT recovery. It is much better than CWM
[HTC Desire S] spankranger:
I downloaded the program Ultimate Multi Tool to make a goldcard.

But the program does not connect with (bricked) phones from hboot or recovery. And without a connection from phone to the program you cannot make a goldcard. :(

The output of the commands: http://pastebin.com/UrZqDGcP
[HTC Desire S] amidabuddha:
Thanks. Now we are going into the Linux universe, modified for Android :) The good news are that if we have the "Attempt to read block from filesystem resulted in short read" error in Linux it means that the system cannot find the proper address, but it is fixable. So lets try to do this for your device:

e2fsck -f -b 32768 /dev/mmcblk0p25
e2fsck -f -b 32768 /dev/mmcblk0p26

post the output here