yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] opumps:
i ran fastboot oem boot, and got these info:

is there anything wrong about my cid?

... 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!
[HTC Desire S] Numline1:
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???).
[HTC Desire S] opumps:
indeed!!!!
[HTC Desire S] szallah:
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...
[HTC Desire S] opumps:
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.
[HTC Desire S] shrome99:
Same happened to me DAMMIT !!! What can i do? Tell me
[HTC Desire S] InfernalByte:
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.
[HTC Desire S] shrome99:
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?
[HTC Desire S] Nipqer:
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
[HTC Desire S] InfernalByte:
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.
[HTC Desire S] dbezzegh:
What solved the issue? I have the same problem... :((
[HTC Desire S] Nipqer:
If you have the broken chip, you'll have to return it and get it replaced under warranty.

-Nipqer
[HTC Desire S] dbezzegh:
How can I be sure if it's a hw problem? I mean, it looks like one, but I would like to be sure...
[HTC Desire S] Numline1:
Try RUU. If it doesn't work and your phone has all the described symptoms, you should return it and have it repaired.
[HTC Desire S] dbezzegh:
Returned the phone

It seems I was also one of the "lucky" DS owners who had a faulty eMMC chip.

I hope it will be fixed... I was S-OFF-ed and I fear for my warranty.
[HTC Desire S] Nipqer:
Everyone I have heard of has had no issues with s-off. If you have an eng-hboot you can brick it nice and proper so as they can't see s-off though.

-Nipqer
[HTC Desire S] dbezzegh:
I could not flash hboot. It wasn't possible neither way:( So I could not hide that i S-OFF-ed. Hope is all I have now. :)
[HTC Desire S] ben_pyett:
Just in case, I ever get in this situation, how would I manage to achieve this, please could you PM me the answer so that it's not in thread, so that someone doesn't think it's something to try out....thanks ;)
[HTC Desire S] opumps:
good question!

now, here is how you would like to be sure:

through

dmesg | grep mmc0

check your eMMC good or bad

(http://xdaforums.com/showpost.php?p=13895268&;postcount=48)

my bad eMMC showed:

<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

<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]
[HTC Desire S] Bubaaak:
I tried this before , but I am still not sure. I've got M4G2DE which is faulty one, but in adb shell I get this - no error.

dmesg | grep mmc0
<3>[ 8.565704] mmc0: No card detect facilities available
<6>[ 8.566223] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.566467] mmc0: Platform slot type: MMC
<6>[ 8.566589] mmc0: 4 bit data mode disabled
<6>[ 8.566711] mmc0: 8 bit data mode enabled
<6>[ 8.566955] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.567077] mmc0: Slot eject status = 0
<6>[ 8.567291] mmc0: Power save feature enable = 1
<6>[ 8.567443] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0ba08000
<6>[ 8.567687] mmc0: DM cmd busaddr 0x0ba08000, cmdptr busaddr 0x0ba08300
<6>[ 8.720886] mmc0: new high speed MMC card at address 0001
<6>[ 8.722167] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Anyway I'm very interested in that if they will repair it for someone under warranty, because I'm S-OFF yet and now I'm worrying pretty much about that...
[HTC Desire S] opumps:
if so, try ENG-HBOOT, [MISC] ENG HBOOT is here !

then try to follow the debug procedures step by step in the #1 post, good luck

when u've done, and nothing changes, try do recover your HBOOT to S-ON mode, if you can.
[HTC Desire S] dbezzegh:
Void warranty

I got my phone back. And as I have feared, without a repair.

Because of S-OFF my warranty is void. :(

So, I have to get it repaired on my cost... (~80$) + no more warranty

So be more careful then me! This battery-pull-n-push can be deadly...
[HTC Desire S] Nipqer:
Did you send it back to htc or someone else?

Maybe you could try explain that its a hardware issue

-Nipqer
[HTC Desire S] dbezzegh:
I brought it to Voda, they gave it to the local HTC service and 10 days! later I got it back with no more warranty because no stock software/S-OFF. I could argue about hw issue and nothing to do with the sw I was running on the phone, but I don't think it will help...

Edit: I called the local HTC service and explained that the problem is a hardware failure. Answer: It does not matter. No warranty because of non stock software... I wrote to HTC to ask them for an official position on this. I will post the answer if I receive it. But if they say the same, I will most likely not buy another HTC phone in the future. It's sad as I am a HTC fanatic and didn't even checked other manufacturers devices as I wanted a new phone only what HTC has to offer...

HTC's answer:

In regards to the repair of your phone, we cannot offer this repair free of charge as when you tamper with the phones software (i.e loading a custom ROM) you void your warranty with us. This is because we cannot accept responsibility for third party software that you choose to load into your phone. We have not tested our phones with this software and thus cannot guarantee they are going to function correctly on your phone, or that they will not cause problems.
[HTC Desire S] Snakeforhire:
Got the same problem as Opumps here. Except in my case it's the /system partition which got somehow ****ed up..

I was customizing my CoreDroid ROM and making a Titanium backup, when all of a sudden one popup after another started appearing onscreen saying "this or that process stopped unexpectedly blahblah" and FC/Retry buttons.

So since I couldn't even raise the shutdown menu anymore, I pulled the battery off -yea I know, at the time I wasn't aware this could be deadly- and rebooted, but got stuck at the HTC loadscreen...

So I thought "meh, no biggie. I'll just restore the backup I took a few hours ago", booted into recovery (4EXT-2.1.0) and tried to restore, and that's when I got the Error (status 1) messages and understood that something was terribly wrong... :(

I tried all night to fiddle with whatever solution I found (restoring HBOOT, flashing a new recovery to recreate the partition table, flashing a stock ROM with RUU -but impossible to downgrade from hboot 1002 to the old one it seems... Nothing works.

What's strange is that dmesg doesn't explicitly show the message ascertaining that the emmc is fried, just that it couldn't read something on it...

Anyone got a backup of a proper mtd0.img (and maybe the other partitions and partition table as well) ? I'll try overwriting the default layout, maybe it'll unbrick it... :/
[HTC Desire S] deadwasp:
my phone with the same mistake installs the new rom installs su but it cannot open

after installing su on recovery i can format system wipe everything and install roms but it cannot opens is there a different or strange thin with my desire s
[HTC Desire S] deadwasp:
one strange thing i can install virtuous but i cannot install lbc mod v.53 which was lastly on my phone

i can install virtuous with recovery but it doesnt boot
[HTC Desire S] boyan.orion:
Had my phone bricked with the flash of the official 1.47.401 ( rooted ) rom.

The samsung chip was completly dead.

I took it to the service and they replaced whole new motherboard, but the sim card could not be detected, then they replaced a new sim board but the phone was badly put together.

I really got pissed off because the power button was stuck and the screen was misaligned so i took my phone apart, all of it just to find that the service forgot to put 2 screws inside so they were missing, and also they put wrong screws at wrong places so there is a little bump on the shell casing because the screw nearly pierced the shell.

I assembled the phone but i am missing now 2 screws lol and i'm getting really sick of it. I see these phones Desire S sometimes dont even power on at all out of the factory when sold as brand new.

I'm disappointed that i have wasted money for it.
[HTC Desire S] touching80:
where did you buy the replacement part?
[HTC Desire S] deadwasp:
cant a chip burn itself by pulling out a battery.i think it only block itself.i think someone who knows everything about smartphones can repair this type of mistake.nobody helped us.we are not professional about software.a repairman in my city said i have a device but i haveto open your device.he connect a device and it will make cid off can it help.may i let to do this i am not so rich to buy second mobile this phone was perfect for me.....i collected money for a long lime to buy please help....
[HTC Desire S] chonthat:
where do you fix your phone ???
[HTC Desire S] geosan1638:
@opumps, where did you buy the Sandisk replacement and how much did it cost?

I have taken out my faulty emmc but can't seem to find a replacement.
[HTC Desire S] chonthat:
nobody can help me ???
[HTC Desire S] relaksua:
Guys..assisting a friend regarding this same problem...can i know this method too before sending back to HTC service centre?? Thank you.
[HTC Desire S] Snakeforhire:
PM me, I'll send it to you.

There's a good chance that it won't work though, if the eMMC is fried it won't be able to flash correctly to it -which is most strange, because flashing back to a stock RUU and HBOOT -if it works and gets applied correctly- seems to "hide" the problem and makes the phone behave like normal..

Tried it this weekend and I couldn't find a single flaw in the behavior of the phone. It's only when you S-OFF and root it again -or try to format the affected partition via the recovery- that it's complaining like hell... :S

And this is most annoying too.. If the phone doesn't show a problem when on S-ON and stock ROM, what'd be your excuse to send it back to the service centre ? :S
[HTC Desire S] ben_pyett:
Have you installed EXT4 recovery and checked the types of file systems that you have on these partitions EXt2/EXT3/ETX4? etc

A different stance would be do the errors ever effect or get in the way of your daily phone use, if not - tempted to ignore them?
[HTC Desire S] vndnguyen:
Hi, my Desire S has the same symptom (same output) as yours. So please confirm if my eMMC was fried or not?

Thanks
[HTC Desire S] Snakeforhire:
Of course, my dear man...

Actually EXT4 was installed there as soon as I rooted the phone. ^^

It's only one of the many things I tried in order to solve it, among reflashing and repartitioning the mtd0, formatting the affected partitions in EXT4 then converting to E3 and back (which makes recovery detect their sizes correctly again, whereas it detected them as "null" before), formatting them manually via 'adb shell root' (using various options like '-cc" to detect the bad blocks and automatically exclude them from the mke2fs.ext4 inode list, and such), using tune2fs to tweak the FS settings... About the only thing I didn't try yet is formatting with btrfs to see if it can circumvent such "shortcomings", which I'm looking into as of now.. :p

"to be continued"... ^^
[HTC Desire S] BratPAQ:
im having same trouble as posted on 1st post. cant mount /data and /cache. getting same error. so does this mean its an eMMC problem?
[HTC Desire S] ben_pyett:
I'm afraid that it does, although you really need to give a little more information, as post #1 contains dozens of varying commands sections and errors...

What happened just prior to you experiencing this problem?- this is part for diagnosis of your issue and part as an attempt to work out what not to do in the future!
[HTC Desire S] Snakeforhire:
I got a ready-made and one-size-fits-all answer to that : 'don't buy HTC hardware, ever, under any circumstance'... :/
[HTC Desire S] ben_pyett:
Sorry for your loss, BUT!

LOL, :D that comment may make you feel better :), yet it isn't of much help for the rest of us :( that still own a working device and therefore may face the problem in the future, these being the same people that were prepared to assist you if we we could :rolleyes:
[HTC Desire S] Snakeforhire:
well that's the whole point : to spare my troubles to some potential HTC buyers (RUN, ye hapless mortals ! Here there be great danger...) :s

sorry if I sound bitter, but paying 250€ for a piece of **** that don't even last for 3 weeks b4 croaking makes u a bit pissed off (and actually want to give back Taiwan to communist china. bcoz if this is taiwanese quality it'll be just as comfy there, and at least we'll pay much less for their crap... :( )
[HTC Desire S] ben_pyett:
When is it time to say something?

Don't feel the need to apologize, if I was in your position, I imagine that I'd wouldn't be so restrained with regard holding back my expletives...:mad:.(I know the forum has rules....but...:p).

With the increasing frequency of this identical problem now happening I'm quite amazed that HTC haven't responded or been inundated with angry/livid users screaming at them demanding action!

Is it due to the fact that we've all S-OFF'd and feel the need to be polite as we're aware that we've knowingly broken our warranties....not that that has anything to do with the problem we have then suffered!

Perhaps it's time to start spamming their Facebook Page with questions as to the quality and reliability of said eMMC chips and see what their plans for the future are......we have seen public action change HTC strategy in the past. Whose is to say that it wouldn't happen again!?
[HTC Desire S] EbiEre:
Sounds like an idea! To find some people doing this on the Facebook page, could help us to get an answer from htc.

If there is more interest I will do it tomorrow.

Cheers
[HTC Desire S] dave303:
Well... after a long night... I had all of the symptoms described by everyone here, however mine came back from the dead after a stock RUU update from fastboot. I *HOPE* at least a small percentage of people were as lucky as me... details on my blog... which I can't link here as this is my first post..

search for it if you're interested (dave heavy industries) for the full recount of events, otherwise the nitty gritty is that after following the instructions to work out of your MMC is screwed, I decided to try and get rid of clockworkmod and try my luck at a warranty job. I couldn't get fastboot to flash boot.img or recovery.img so instead I ran the htc telstra RUU while the phone was in fastboot and BLAMMO! success.

Re-rooted, Re flashed, now 100% up and running... very happy (relieved) camper.
[HTC Desire S] BratPAQ:
someone should take note of this and make it sticky, as one of the solution to try, running RRUU while the phone is in fastboot.
[HTC Desire S] Snakeforhire:
Hmm... Me thinks you're getting your hopes up a bit too much..

I experienced the same kind of situation reversal as you did, only to find out that when re-rooted, my DS was just as quirky as before..

It's not giving any "hard errors" messages per se, it's way more insidious than this..

It's all about the phone being generally much more sluggish as before, often lingering at 90-100% CPU (and for a good cause : it has to write the same blocks/inodes X number of times before they actually get written correctly), apps mysteriously "disappearing" (=shown as "not installed" in app manager, or "on SD-card") when they're supposed to be in the internal memory, and so on.

Try connecting to your phone via an adb rootshell console, and do a manual cache wipe on the affected partition(s) (mke2fs.ext4 with your own options if you like, like '-cc', 'writeback' and such), and see if it gives you any errors when formatting it.

I'd bet one of my testi..fingers that it will, it's almost guaranteed.

I'd really love it to be different and to be able to give you hope about this, but sadly, once an eMMC is fried there's no magic "back" button to go back in time... :/
[HTC Desire S] mugen71:
Previously when i face the same problem, event running the stock RUU update from fastboot doesn't help. It hang halfway.
[HTC Desire S] dave303:
I'm not saying that my emmc magically un-fried itself (thats crazy!), I'm suggesting that mine was never fried in the first place - although according to the tests provided at the beginning of this thread, it was. I'm also suggesting that something about the htc provided RUU has helped, and if you happen to be in this boat, it certainly wouldn't hurt to try :) fyi - the phone has been operating for about 7 hours without trouble so far. I'll advise if this changes over the next few days.

Snakeforhire:--

~ # mke2fs -j /dev/block/mmcblk0p27

mke2fs -j /dev/block/mmcblk0p27

mke2fs 1.40.8 (13-Mar-2008)

/dev/block/mmcblk0p27 is apparently in use by the system; will not make a filesy

stem here!

~ # umount /cache

umount /cache

~ # 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 35 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

~ # e2fsck /dev/block/mmcblk0p27

e2fsck /dev/block/mmcblk0p27

e2fsck 1.41.6 (30-May-2009)

/dev/block/mmcblk0p27: clean, 11/76912 files, 20003/307196 blocks

~ # e2fsck /dev/block/mmcblk0p27 -f

e2fsck /dev/block/mmcblk0p27 -f

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), 20003/307196 blocks
[HTC Desire S] chris5s:
Glad to hear it mate. There's

far

too many scaremongers on here willing to wave the "your emmc chip is fried" in peoples' faces without thinking.

Peace
[HTC Desire S] rakmok:
I have fired eMMc chip.

Please help me. Which Sandisk chip i have to buy (below is the URL) and what is the cost?

http://www.sandisk.com/business-solutions/inand-embedded-flash-drives