You would be writing a letter notifying the claim and then pursuing it, it depends on a few factors.
You would be writing a letter notifying the claim and then pursuing it, it depends on a few factors.
Where do I send the letter? Who do I write the letter for?
What does pursuing it exactly mean? Does this involve lawyers?
I don't know where you can get it done, but i'm sure you don't wanna know how much does it cost... It's way too expensive as for eMMC chip :-(
Sent from my HTC Desire S using xda premium
hi guys
im going to get a desire S
how do i check if i have a faulty emmc without root?
i want to find out before trying to root and s-off
im going to get a desire S
how do i check if i have a faulty emmc without root?
i want to find out before trying to root and s-off
t's probably a bit late for you but it might help others : whe
this happens, try killing the fastboot and adb processes in windows ' task manager ( don't worry it would brick your device, if the emmc is fried it can't get much worse, and you can always reflash another rom as long as there's an viable hboot). for me it succeeded in unblocking the flash a few times. Those two processes start up again by themselves and will restart in emergency recovery mode, it might work better if the memory is still writable.
[Solved] Without replacing eMMC
I ran the tests stated and my G2 reported "Deferred resume failed"
I then successfully resolved the issue with 2 fastboot commands:
1. fastboot oem rebootRUU
2. fastboot flash zip PC10IMG_Vision_TMOUS_2.15.531.3_Radio_12.52.60.25U _26.08.04.30_M3.zip'
Link to PC10IMG here
Please let me know the success rate for you
I ran the tests stated and my G2 reported "Deferred resume failed"
I then successfully resolved the issue with 2 fastboot commands:
1. fastboot oem rebootRUU
2. fastboot flash zip PC10IMG_Vision_TMOUS_2.15.531.3_Radio_12.52.60.25U _26.08.04.30_M3.zip'
Link to PC10IMG here
Please let me know the success rate for you
Catching the thread incidentally, haven't read all the latest developments, but to answer your question : Most likely. the Desire S and the G2/DesireZ are very similar as far as hardware goes. YMMV but by and large this holds true for .zipfiles that don't need a very low-level hardware access (=most of them, in practice).
hi..
i m the user of Riff and i m triyng to repair it by USB DCC Loader and after second restart the phone pc detects is as Unknown Device if i use the TP pc detect the device as Riff USB DCC Loader but this time not detecting the Flash ic.. this mean flash ic is totaly damaged. so i need to replace it..
thanx...
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..
Ok. You can buy emmc here: http://www.parts4repair.com/htc-desire-s-sandisk-sdin5c2-4g-flash-chip-wit/
U can try this: http://xdaforums.com/showthread.php?t=1756287
Sent from my fried HTC Desire S using xda app-developers app
Sent from my fried HTC Desire S using xda app-developers app
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
4hi 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.
"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://xdaforums.com/showpost.php?p=16135893&postcount=27
A eMMC design flaw, Confirming info from htc-offical (thanks apairofscissors)
http://xdaforums.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]
[ wipe cache ]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_log2. [ install zip from sdcard ]Code:Formating /cache... Cache wipe complete. E:Can't open /cache/recovery/log E:Can't open /cache/recovery/last_log3. [ backup and restore ]Code:-Checking Model ID -success! -Model ID - HTC sage Now flashing E:Error in /sdcard/*******.zip (Status 1) Installation aborted.4. [ RUU+Goldencard ]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
Goldencard is good, in FASTBOOT USB mod,
passed the (version) checking, updating 1.28.401.1 to 1.47.950.3, but stuck at5. [ ROM.zip->PG88IMG.zip ]Code:rebooting bootloader ...... upgrading ROM image in your Android Phone... Please do NOT disconnect USB cable nor run any program.
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
DS-brick showsCode: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)
it means the filesystem on eMMC was accidentally broke down. so, im trying to restore the filesystem, and get these: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]
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
format /system with type ext3Code:~ # 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 /data with type ext3Code:~ # 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]
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].3Well... 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.2Cliff notes: I think the Hboot “Factory Reset” option cured my problem.
Details:
I had lots of “status 1″ errors and phone wouldn’t go past the white HTC logo. I was about to start looking for RUUs when I did this:
I turned off the phone again (using the trick of volumeup/volumedown/power buttons together) and quickly removed the battery again.
I rebooted into Hboot (volumedown/power together). From there, just for the heck of it, I selected the “Factory Reset” option. (I’m on the Hboot installed by the Revolutionary tool http://revolutionary.io/, don’t know if ALL Hboots have this option). I didn’t know if this would be different than the recovery tool wipe, but I thought I’d try.
After I selected this the phone rebooted and went to recovery. When I tried to reinstall the CM 7.1 ROM zip, which failed previously with status 1, it worked.
Phone seems fine now. Hope this helps someone.11The easiest way to rectify is to RUU and start over. Unless you enjoy the frustration!
