Hello! I have the HTC Desire S and it does that problem! I erased the system, data and cache partitions via fastboot but when I boot into recovery to flash the new ROM I face the problem.
I see:
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant mount cache/recovery/last_log
When I try to install the ROM from my sdcard it says " E:can't mount/sdcard.
What sould I do now? Tried flashing new recovery, went well but still I get the same error. Even reflashed the hboot via fastboot.
fastboot finds my phone. But I noticed that when I am in HBOOT the device is not scanning for the update files as it normally should do.
I checked the sdcard and the problem doesnt come from it.
What to do now? Thanks inadvance!
Greetings, Simeon.
sssimo96 said:
Hello! I have the HTC Desire S and it does that problem! I erased the system, data and cache partitions via fastboot but when I boot into recovery to flash the new ROM I face the problem.
I see:
E:can't mount /cache/recovery/command
E:cant mount /cache/recovery/log
E:cant mount cache/recovery/last_log
When I try to install the ROM from my sdcard it says " E:can't mount/sdcard.
What sould I do now? Tried flashing new recovery, went well but still I get the same error. Even reflashed the hboot via fastboot.
fastboot finds my phone. But I noticed that when I am in HBOOT the device is not scanning for the update files as it normally should do.
I checked the sdcard and the problem doesnt come from it.
What to do now? Thanks inadvance!
Greetings, Simeon.
Click to expand...
Click to collapse
The error messages could mean, that the partition cache is corrupted. Which recovery do you use?
You said, flashing of ROM was unsuccessfull? If not, does booting work?
Have you ever flashed a ROM and got it working? Does flashing another ROM work?
Does that not mean a fried emmc chip? Im sure those error mean that. @ op go to development thread and look at the thread by ben_pyett (rom + guides thread) and go down to the bottom n ul see the links bout fried emmc chip.
I have flashed many ROMs. The problem is that the phone cannot locate the sdcard partition. I already fixed the cache partition but the problem with the sdcard is still present. Will try to push the ROM to the cache partition and then flash it with TWRP recovery.
But anyway is there any chances to fix the error mounting sdcard?
Edit: I think its not fried emmc chip. the command
dmesg | grep mmc0
leads to Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Mimi>cd\adb\platform-tools
C:\adb\platform-tools>adb shell
~ # ←[6ndmesg | grep mmc0
dmesg | grep mmc0
<3>[ 5.873718] mmc0: No card detect facilities available
<6>[ 5.874328] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 5.874481] mmc0: Platform slot type: MMC
<6>[ 5.874725] mmc0: 4 bit data mode disabled
<6>[ 5.874847] mmc0: 8 bit data mode enabled
<6>[ 5.875000] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 5.875244] mmc0: Slot eject status = 0
<6>[ 5.875366] mmc0: Power save feature enable = 1
<6>[ 5.875610] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x0c3e4000
<6>[ 5.875732] mmc0: DM cmd busaddr 0x0c3e4000, cmdptr busaddr 0x0c3e4300
<6>[ 6.028350] mmc0: new high speed MMC card at address 0001
<6>[ 6.029418] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ # ←[6n
Well, this could mean your SDcard isn't connected or it is broken. But you said you checked that already.. well if you can get a ROM running you will then could check if you have access to your card.
I start thinking that there is some hardware issue. I just replaced my digitizer so I could have damaged the part that holds the SIM card and the SD. But is it possible the problem to be from the motherboard? If not then I will order new SIM/SD part from ebay and will replace it.
Of course it is but unlikely cause these parts aren't that sensitive. First of all make sure that it is really a hardware issue before you buy anything you don't need.
So I flashed the ICS RUU and the phone works well except for the SD card. So I guess its hardware related. Will buy the SIM/Sd holder but what I am thinking is if it is possible to be something from the motherboard because the SIM works well. Probably the SD slot is broken or the cable is damaged
Related
Got a strange problem....
If I press up/down volume when the phone is supposed to be locked it turns the screen on. Obviously if my phone is in my pocket this is going to happen all the time and waste the battery etc.
Any ideas how I can prevent this from happenning?
cheers.
Thats a feature, not a bug
I know on MIUI-rom you can turn it off in settings, which rom are you using?!
I'm using Shadow Hawk v2.1
Looked everywhere for a setting, just can't find it.
I never tried that rom, but in the thread where to download shadow hawk you should have a look in the feature list
Code:
*Wake phone with volume keys (thanks to lowveld)
tangerine0072000 said:
Got a strange problem....
If I press up/down volume when the phone is supposed to be locked it turns the screen on. Obviously if my phone is in my pocket this is going to happen all the time and waste the battery etc.
Any ideas how I can prevent this from happenning?
cheers.
Click to expand...
Click to collapse
Hmmm...Maybe you can turn off this option from within RCMix tweaks, if you enabled it from there. I've never used that ROM, but i understand that it uses RCMix tweaks and it would do you good to find out if there is a volume wake setting in there. If there isn't, i have the fix for it, and i can give it to you if you're willing to try it. First let me know if you can find anything in the RCMix tweaks.
Cheers
thanks chaps, I had a look in RC tweaks initially before posting, but there is nothing in there that refferences the volume controls.
by the way, what was the fix ?
tangerine0072000 said:
by the way, what was the fix ?
Click to expand...
Click to collapse
Well, the solution is to replace android.policy.jar with the attached file.
This is located in system/framework
Use root explorer or es file explorer with root access, mount system as r/w and replace the said file in the above folder with the one below. Reboot. That's it...your volume buttons will just function as normal volume rocker, and will not wake the phone up anymore.
P.S. : While i don't expect any problem at all, i would highly recommend taking a nandroid backup, and also backing up your original android.policy.jar in case something goes wrong, or you want to revert back to volume rocker wake... Do post back if it works for you.
CLICK TO DOWNLOAD
thanks for the info, I got the download. I tried mounting through these apps, but can't find an option for it. Do I need to mount read/write via the ADB ?
Not done this procedure before.
thanks,
I managed to replace the file using 'root explorer'. Did a reboot, but still got the problem with the volume switching the screen on.
so in my infinate wisdom I thought I might as well put the orignal file back which I did and rebooted. Then the phone wouldn't boot, stuck on HTC logo.
Then I thought I would restore my nandroid back (which I made last night). Phone will only still boot to HTC screen. Doh !
Did this serveral times, formating, clearing cache, restoring backup, but still no joy.
You should read this thread!
edit:
another guide
think I have corrupted cache as I know get....
E:Can't open /cache/recovery/log comming alot when trying to do anything in recovery mode.
tangerine0072000 said:
think I have corrupted cache as I know get....
E:Can't open /cache/recovery/log comming alot when trying to do anything in recovery mode.
Click to expand...
Click to collapse
did you read the guides of my last post? they are may solving your problems!
really wiered.
when I do 'dmesg | grep mmc0' I just get the command prompt...
~ # dmesg | grep mmc0
dmesg | grep mmc0
~ #
I contined to perform 'mke2fs /dev/block/mmcblk0p27'
~ # mke2fs /dev/block/mmcblk0p27
mke2fs /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
Writing superblocks and filesystem accounting information:
done
This filesystem will be automatically checked every 36 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override
~ #
then tried to install my rom which failed part way through.
I am now getting some response from ADB, no errors that I can see.
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 6.994781] mmc0: No card detect facilities available
<6>[ 6.995300] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 6.995544] mmc0: Platform slot type: MMC
<6>[ 6.995666] mmc0: 4 bit data mode disabled
<6>[ 6.995819] mmc0: 8 bit data mode enabled
<6>[ 6.996032] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 6.996154] mmc0: Slot eject status = 0
<6>[ 6.996398] mmc0: Power save feature enable = 1
<6>[ 6.996520] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2c8000
<6>[ 6.996765] mmc0: DM cmd busaddr 0x0c2c8000, cmdptr busaddr 0x0c2c8300
<6>[ 7.150024] mmc0: new high speed MMC card at address 0001
<6>[ 7.151672] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Hi, I believe I corrupted my cache after writing some files to /system/framework in read/write mode.
As I now get the infamous 'can't open /cache/recovery/log when formatting etc
Phone will longer boot....1
1. don't get any errors using adb and 'dmesg | grep mmc0', I get ..
dmesg | grep mmc0
<3>[ 6.994781] mmc0: No card detect facilities available
<6>[ 6.995300] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 6.995544] mmc0: Platform slot type: MMC
<6>[ 6.995666] mmc0: 4 bit data mode disabled
<6>[ 6.995819] mmc0: 8 bit data mode enabled
<6>[ 6.996032] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 6.996154] mmc0: Slot eject status = 0
<6>[ 6.996398] mmc0: Power save feature enable = 1
<6>[ 6.996520] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2c8000
<6>[ 6.996765] mmc0: DM cmd busaddr 0x0c2c8000, cmdptr busaddr 0x0c2c8300
<6>[ 7.150024] mmc0: new high speed MMC card at address 0001
<6>[ 7.151672] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
2. Gone through all the usual process of using clockwork recovery, wiping cache formating etc.
3. My phone was s-off'd using revolutionary, tried running that again, but keeps reffering to a missing /sbin
4. Tried various images renamed as PG88IMG.zip which start to update, but just stay in 'updating' and never move forward. To unlude 4ext recovery image.
5. Tried installing 4ext using 'fastboot flash c:\recovery image', but it just says waiting on device.
running out of idears before I declare it bricked.
I got similar problem while ago, but I could boot with no problems, advanced showed same for me, but then I manage to flash 4ext recovery and I format all partitions to ext4 but when I did cache same errors, I wiped only cache and do it again, all works now no problem, havnt tryed to instal new rom, got some good one.
Sent from my HTC Desire S using xda premium
Ok I have searched through all the relevant eMMc fried posts however I have not found a similar post to this with the same cmd return so you help would be appreciated..
After the dmesg grep command this was what the cmd returned...
Code:
C:\android-tools\android-tools>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 7.922210] mmc0: No card detect facilities available
<6>[ 7.922760] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.923004] mmc0: Platform slot type: MMC
<6>[ 7.923126] mmc0: 4 bit data mode disabled
<6>[ 7.923339] mmc0: 8 bit data mode enabled
<6>[ 7.923492] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.923736] mmc0: Slot eject status = 0
<6>[ 7.923858] mmc0: Power save feature enable = 1
<6>[ 7.923980] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2d3000
<6>[ 7.924224] mmc0: DM cmd busaddr 0x0c2d3000, cmdptr busaddr 0x0c2d3300
<6>[ 8.077545] mmc0: new high speed MMC card at address 0001
<6>[ 8.079345] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
Is this a fried chip or some other issue?
I am still getting the usual fried error in the bootloader:
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
Currently running:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
Thanks for your help.
Your eMMC is fine.
Wipe your /cache from recovery. Use 4EXT
veejayjameson said:
Ok I have searched through all the relevant eMMc fried posts however I have not found a similar post to this with the same cmd return so you help would be appreciated..
After the dmesg grep command this was what the cmd returned...
Code:
C:\android-tools\android-tools>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 7.922210] mmc0: No card detect facilities available
<6>[ 7.922760] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.923004] mmc0: Platform slot type: MMC
<6>[ 7.923126] mmc0: 4 bit data mode disabled
<6>[ 7.923339] mmc0: 8 bit data mode enabled
<6>[ 7.923492] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.923736] mmc0: Slot eject status = 0
<6>[ 7.923858] mmc0: Power save feature enable = 1
<6>[ 7.923980] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c2d3000
<6>[ 7.924224] mmc0: DM cmd busaddr 0x0c2d3000, cmdptr busaddr 0x0c2d3300
<6>[ 8.077545] mmc0: new high speed MMC card at address 0001
<6>[ 8.079345] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
Is this a fried chip or some other issue?
I am still getting the usual fried error in the bootloader:
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
Currently running:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
Thanks for your help.
Click to expand...
Click to collapse
Try wipe the whole phone and install a new rom xD
massi99 said:
Try wipe the whole phone and install a new rom xD
Click to expand...
Click to collapse
+1 Yup, that would be my advice too... it's just your cache partition that gone tits-up, and i think a format of the cache should solve it. But why not just be double sure and nuke all the bloody partitions and do a clean flash!
massi99 said:
Try wipe the whole phone and install a new rom xD
Click to expand...
Click to collapse
apk24 said:
+1 Yup, that would be my advice too... it's just your cache partition that gone tits-up, and i think a format of the cache should solve it. But why not just be double sure and nuke all the bloody partitions and do a clean flash!
Click to expand...
Click to collapse
Only one of the "all the bloody partitions" can give this error. Guess which one is it...
But nothing against the double sure, full wipe and clean install of new ROM should solve this for sure
I recommend to use 4EXT Recovery to convert all partitions to ext4 filesystem, then format/wipe all of them, then install a new ROM
But if he wants to keep the present ROM, just wiping cache is the solution...
amidabuddha said:
Only one of the "all the bloody partitions" can give this error. Guess which one is it...
But nothing against the double sure, full wipe and clean install of new ROM should solve this for sure
I recommend to use 4EXT Recovery to convert all partitions to ext4 filesystem, then format/wipe all of them, then install a new ROM
But if he wants to keep the present ROM, just wiping cache is the solution...
Click to expand...
Click to collapse
My favorite savior of bricked devices!
Wherever there's a potential brick, i find you there... maybe i'm vain, but it sure does make me feel secure knowing that there is someone like you around at the DS forum!
I have the same problem. I think my cache partition is corrupted. But after many try I can't format it. It take long time to format.
Also I cant flash 4ext or anything else via adb, fastboot or clockworkmod.
Can HTC service center solved this? Or they will just change the whole PCB?
Plz help me.
Sent from my HTC Legend using xda premium
enigmaamit said:
My favorite savior of bricked devices!
Wherever there's a potential brick, i find you there... maybe i'm vain, but it sure does make me feel secure knowing that there is someone like you around at the DS forum!
Click to expand...
Click to collapse
+1 to that !
History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).
In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
Is the phone stuffed or is there anything else I can try?
col320ce said:
History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).
In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
Is the phone stuffed or is there anything else I can try?
Click to expand...
Click to collapse
Ate you still able to boot into recovery?? Try full wiping your phone
Sent my thoughts to your head with XDA App
i'm no expert, but i'm pretty sure there is still bunch of options for you...
search trough forum, even try to install stock roms (ruu)
chin up!
I have tried a full wipe but will try a .RUU file.
I can get into recovery and move about...
Just tried installing from .RUU file using FASTBOOT USB and RUU from computer. And it won't get past the first screen - "Rebooting to bootloader.........."
After all I have done it still tells me I have Software version 1.47.832.1 installed.
col320ce said:
History:
Desire S rooted using "revolutionary-0.4pre4" but otherwise no changes (rooted many months ago).
Crashed during update of Apps (I pressed update all and it crashed it after a few minutes). Had to pull the battery out to reset. Crashed again after about 2 minutes so I pulled the battery again and now won't load past the HTC loading screen.
I assume something fried as I pulled the battery.
I have tried updating the ROM without success - just to confirm I am doing it properly I put the file onto the phone's normal SD card (eg "RunnymedeS-Saga-v6.zip"), start recovery mode, wipe data and cache and load from zip file.
It either finishes loading or says there is a problem with the zip file (I've tried 5 or so ROM files). on the times it managed to finish it resets and just gets stuck on the HTC load screen (like before).
In Recovery mode I have:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
Is the phone stuffed or is there anything else I can try?
Click to expand...
Click to collapse
Can you enter the custom recovery at all?
If so, do the following and post your result so first we can rule out an eMMC problem.
Set up adb (link in my sig) connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
adb shell
dmesg | grep mmc0
Source : Amidabuddha's excellent guide here : http://forum.xda-developers.com/showthread.php?t=1284196
I can enter recovery and I am on the screen with "HBOOT USB PLUG" when plugged into the PC.
I have set up the abd link but it cmd says "error: device not found"
I assume I have not installed adb correctly or am not in the correct part of the command prompt. Do I need to go to C:/android-tools/ then type adb shell or does it not matter?
When I type
adb shell
dmesg | grep mmc0
I assume I hit return after the first line?
How do I type the vertical line in the second line?
I have HTC Sync Installed
I have the folder at c drive root - c:\android-tools\
I have put a copy of the content of the folder into windows\sytem32
I can't see the phone in "my computer" when it is attached by USB.
???
Just got it to work
C:\Documents and Settings\Person>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 8.471618] mmc0: No card detect facilities available
<6>[ 8.472259] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.472412] mmc0: Platform slot type: MMC
<6>[ 8.472625] mmc0: 4 bit data mode disabled
<6>[ 8.472747] mmc0: 8 bit data mode enabled
<6>[ 8.472991] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.473114] mmc0: Slot eject status = 0
<6>[ 8.473236] mmc0: Power save feature enable = 1
<6>[ 8.473480] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c1fa000
<6>[ 8.473602] mmc0: DM cmd busaddr 0x0c1fa000, cmdptr busaddr 0x0c1fa300
<6>[ 8.626892] mmc0: new high speed MMC card at address 0001
<6>[ 8.628082] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #
I don't think this is a good sign.
thanks
col320ce said:
I can enter recovery and I am on the screen with "HBOOT USB PLUG" when plugged into the PC.
???
Click to expand...
Click to collapse
There is a difference between being in the bootloader and Recovery.xCan you boot into recovery?
col320ce said:
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #
Click to expand...
Click to collapse
Sorry man.
col320ce said:
I assume something fried as I pulled the battery.
Click to expand...
Click to collapse
Another proof that this is a dangerous action on Desire S
col320ce said:
Just got it to work
C:\Documents and Settings\Person>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 8.471618] mmc0: No card detect facilities available
<6>[ 8.472259] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.472412] mmc0: Platform slot type: MMC
<6>[ 8.472625] mmc0: 4 bit data mode disabled
<6>[ 8.472747] mmc0: 8 bit data mode enabled
<6>[ 8.472991] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.473114] mmc0: Slot eject status = 0
<6>[ 8.473236] mmc0: Power save feature enable = 1
<6>[ 8.473480] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c1fa000
<6>[ 8.473602] mmc0: DM cmd busaddr 0x0c1fa000, cmdptr busaddr 0x0c1fa300
<6>[ 8.626892] mmc0: new high speed MMC card at address 0001
<6>[ 8.628082] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 9.837493] mmc0: Failed to get card ready i = 122109
<6>[ 9.837585] mmc0: reinit card
<4>[ 9.837707] mmc0: Starting deferred resume
<6>[ 11.879486] mmc0: Deferred resume failed
<3>[ 11.881774] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.882141] mmc0: Controller has been reset
<6>[ 11.882324] mmc0: Worked around bug 1535304
<3>[ 11.883758] mmc0: DMA channel flushed (0x80000004)
<6>[ 11.884094] mmc0: Controller has been reset
<6>[ 11.884368] mmc0: Worked around bug 1535304
<6>[ 11.890960] mmc0: reinit card
<4>[ 11.891052] mmc0: Starting deferred resume
<6>[ 13.931549] mmc0: Deferred resume failed
~ #
I don't think this is a good sign.
thanks
Click to expand...
Click to collapse
Ouch!
eMMC most likely dead. I'm real sorry man... wish there was anything further i could suggest....
You'll have to take it to the Service Centre, and hope for the best.
I still don't understand, that after all the warnings against pulling battery, why do so many users do it? It baffles me. Honest to God, i still have to figure that behavior out... It's like wanting to brick your phone.
I usaly leave debugging on all the time. If it hangs 3 button combo or clear catches with adb and then restart it. Never pull battery out, if you don't have access to PC then leave it and do it later, better do it without risk. And you got faulty emmc before becouse it hanged on app upgrade. Sorry mate
Sent from my HTC Desire S using xda premium
Is pulling the battery the only way to brick the m4g2de emmc chip or can it just happen on its own?
incrediblealex said:
Is pulling the battery the only way to brick the m4g2de emmc chip or can it just happen on its own?
Click to expand...
Click to collapse
Here is a post about what can brick it. Many things can fry it. But still Never pull out battery
Sent from my HTC Desire S using xda premium
I can enter bootloader but the computer can't find the phone unless I go into the RECOVERY (revolutionary CWM v4.0.1.4). I assume the text printout is still valid?
In bootloader (after vol down and on) I attach the USB and the screen says (amongst other things) HBOOT USB PLUG (from HBOOT).
C:\>adb shell
error: device not found
Unless anyone thinks the phone is not stuffed, can I brick it further to stop the HTC repair man seeing that it is S-OFF? I have tried to remove revolutionary and S-OFF but can't get anything to work.
Not sure If you can brick it further since your emmc is where you write all of the files
Hello,
Will installing a new rom on my S-OFF Desire S, it has been a glitch and I've removed the battery to reboot the phone. Now I'm stuck at the "htc logo step".
After some investigation it appears that neither /cache nor /data are now mountable.
I've been think that my eMMc card (which belongs to the faulty serie (M4G2DE)) may have been fried. How ever It appears it is not the case since using adb shell to issue
Code:
# cat /proc/kmsg | grep mmc0
Code:
<3>[ 10.141387] mmc0: No card detect facilities available
<6>[ 10.142028] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 10.142150] mmc0: Platform slot type: MMC
<6>[ 10.142395] mmc0: 4 bit data mode disabled
<6>[ 10.142517] mmc0: 8 bit data mode enabled
<6>[ 10.142639] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 10.142883] mmc0: Slot eject status = 0
<6>[ 10.143005] mmc0: Power save feature enable = 1
<6>[ 10.143249] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0b8c8000
<6>[ 10.143371] mmc0: DM cmd busaddr 0x0b8c8000, cmdptr busaddr 0x0b8c8300
<6>[ 10.296691] mmc0: new high speed MMC card at address 0001
<6>[ 10.297943] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<3>[ 34.849822] mmc0: Failed to get card ready i = 126959
<6>[ 34.850036] mmc0: reinit card
<4>[ 34.850128] mmc0: Starting deferred resume
<6>[ 36.891876] mmc0: Deferred resume failed
<3>[ 60.337951] mmc0: DMA channel flushed (0x80000004)
<6>[ 60.338317] mmc0: Controller has been reset
<6>[ 60.338562] mmc0: Worked around bug 1535304
<3>[ 60.339935] mmc0: DMA channel flushed (0x80000004)
<6>[ 60.340301] mmc0: Controller has been reset
<6>[ 60.340545] mmc0: Worked around bug 1535304
<6>[ 60.347320] mmc0: reinit card
I've tried to clean the file systems using e2fsck but also to make brand new fs using mke2fs and mkfs.ext2, these processes have be able to run, but the mount still fails :
mount: mounting /dev/block/mmcblk0p26 on /data failed: Invalid argument
Click to expand...
Click to collapse
I've been going through several thread here and there : http://forum.xda-developers.com/showthread.php?t=1305950 ; http://forum.xda-developers.com/showthread.php?t=1456036 ; http://forum.xda-developers.com/showthread.php?t=1854558
there is some tips inhere but no working solution, have you any suggestions ? Is there any way to "go back" to standard settings for theses two partitions ?
Thanks a lot !
François.
Can you boot to recovery? If so, have you tried formatting the partitions from there?
Sent from my Desire S using xda app-developers app
Can you boot to recovery? If so, have you tried formatting the partitions from there?
Click to expand...
Click to collapse
Yes I can boot to recovery, and I've tried formatting cache/data partitions, it was not successful.
Should I give it a try with ADB shell ?
Thanks for helping !
F.
[email protected] said:
Yes I can boot to recovery, and I've tried formatting cache/data partitions, it was not successful.
Should I give it a try with ADB shell ?
Thanks for helping !
F.
Click to expand...
Click to collapse
Try 4EXT Recovery if you are using different.
Another solution is to flash a RUU it will restore everything. But be carefully for the version, it has to be the same or higher of your current one
EDIT: looked at the first post and I am sorry to say this but your EMMC is corrupted.
Code:
<3>[ 34.849822] mmc0: Failed to get card ready i = 126959
<6>[ 34.850036] mmc0: reinit card
<4>[ 34.850128] mmc0: Starting deferred resume
<6>[ 36.891876] mmc0: Deferred resume failed
Read carefully through this thread there is a scanner that analyzes corrupted emmc card and it *may* (if you are lucky) to isolate the bad blocks and allows to use the device again with a bit shortened storage. No guarantees. The other way is a replacement of the chip - you can find one here
amidabuddha said:
EDIT: looked at the first post and I am sorry to say this but your EMMC is corrupted.
Click to expand...
Click to collapse
My should question should have been "is my eMMC corrupted", thanks for carefully reading my post.
I'll give a try to the software solution ASAP, thanks for pointing it out !
Read carefully through this thread there is a scanner that analyzes corrupted emmc card and it *may* (if you are lucky) to isolate the bad blocks and allows to use the device again with a bit shortened storage. No guarantees. The other way is a replacement of the chip - you can find one here
Click to expand...
Click to collapse
Scan have been able to go through the whole eMMC's partitions. I would like to believe that the eMMC is still some how usable, but it can't use them. Should I try to "shift" the partitions, to try to get ride of the old file system ?
Thanks again,
F.
[email protected] said:
Scan have been able to go through the whole eMMC's partitions. I would like to believe that the eMMC is still some how usable, but it can't use them. Should I try to "shift" the partitions, to try to get ride of the old file system ?
Thanks again,
F.
Click to expand...
Click to collapse
Sorry it didn't helped. Unfortunately I am not aware of any other method besides replacement to suggest
Sent from my HTC Desire S
There are a few threads were they use the sd card to load a rom with fried emc. I don't know anything more about it.
Sent from my Desire S using xda app-developers app
There are a few threads were they use the sd card to load a rom with fried emc. I don't know anything more about it.
Click to expand...
Click to collapse
Yeah this one for example http://forum.xda-developers.com/showthread.php?t=1756287
but I fail using the provided boot.img with fastboot
The other way is a replacement of the chip - you can find one here
Click to expand...
Click to collapse
Since the eMMC seems to be badly fried, I'm now considering physical replacement. So I've watched the following disassembly video : http://www.youtube.com/watch?v=W7sp3gN-vc0
It does not show the mother border without it's protections, so I am wondering what I'll have to do once the protection removed ? any soldering work ?
A last question about the site you've mentioned (parts4repair.com) is it reliable ?
[email protected] said:
Yeah this one for example http://forum.xda-developers.com/showthread.php?t=1756287
but I fail using the provided boot.img with fastboot
Since the eMMC seems to be badly fried, I'm now considering physical replacement. So I've watched the following disassembly video : http://www.youtube.com/watch?v=W7sp3gN-vc0
It does not show the mother border without it's protections, so I am wondering what I'll have to do once the protection removed ? any soldering work ?
A last question about the site you've mentioned (parts4repair.com) is it reliable ?
Click to expand...
Click to collapse
Luckily I have never ordered a chip for myself but this site was referenced from another users in the past. It is even shipped with a bootloader preinstalled so you just have to put it into the device.
As per the soldering process IMO is best to use a services of a skilled technician to do the job
Sent from my HTC Desire S