Root EMMC is corrupted. NEED HELP

[lepa71]

Hi

I have rezound with s-on. I was on Carbon JB rom. Yesterday I rebooted my phone and it would boot up. It would go to HTC white screen and then blank. I still have access to fastboot and I can boot into recovery, but recovery can't mount internal storage at all.

I tried to lock and run RUU, but I'm on latest HBOOT and RUU fails. I can't downgrade because I'm s-on.

So my question is:
Can I flash partitions with fastboot or reformat emmc?

Any other ideas are welcome?

Thanks
if I try to wipe I get this
E: Can't mount /dev/block/mmcblk0p35

 

[scotty85]

accoerding to a cat /proc/emmc partition 35 is "userdata" so it makes some sense that the wipe fails if it cant mount that partition.

unfortunately,you are limited to what you can do in fastboot by s on. you can try:
fastboot erase userdata

and see if that helps. if you can get to recovery,you can do the following to check the state of your emmc:

enter recovery

open cmd

adb devices
adb shell
dmesg | grep mmc0

good output(gsm 3d with ext 4 recovery):

c:\miniadb_shooteru>[COLOR="Red"]adb shell[/COLOR]
~ # [COLOR="red"]dmesg | grep mmc0[/COLOR]
dmesg | grep mmc0
<3>[    2.973723] mmc0: No card detect facilities available
<6>[    2.974150] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18

<6>[    2.974333] mmc0: Platform slot type: MMC
<6>[    2.974455] mmc0: 8 bit data mode enabled
<6>[    2.974638] mmc0: 4 bit data mode disabled
<6>[    2.974730] mmc0: polling status mode disabled
<6>[    2.974852] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[    2.975035] mmc0: Slot eject status = 0
<6>[    2.975127] mmc0: Power save feature enable = 1
<6>[    2.975310] mmc0: DM non-cached buffer at ff007000, dma_addr 0x570ac000
<6>[    2.975432] mmc0: DM cmd busaddr 0x570ac000, cmdptr busaddr 0x570ac300
<6>[    3.099577] mmc0: new high speed MMC card at address 0001
<6>[    3.100005] mmcblk0: mmc0:0001 KLL00M 2.25 GiB
~ #

bad output(from internet):

mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed

if the fastboot erase command fails,and your emmc shows good,we could try and dd an empty partition 35 to the phone,since you should have a adb daemon and root shell in recovery. again,however, there may well be write protections in place that keep that partition from being written while s on.

 

[scotty85]

for S&Gs,heres the output from my rezound:

C:\Users\Scott>[COLOR="Red"]adb shell[/COLOR]
~ # ←[6n[COLOR="red"]dmesg | grep mmc0[/COLOR]
dmesg | grep mmc0
<3>[    5.554685] mmc0: No card detect facilities available
<6>[    5.556973] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18

<6>[    5.557157] mmc0: Platform slot type: MMC
<6>[    5.557309] mmc0: 8 bit data mode enabled
<6>[    5.557462] mmc0: 4 bit data mode disabled
<6>[    5.557614] mmc0: polling status mode disabled
<6>[    5.557797] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[    5.557950] mmc0: Slot eject status = 0
<6>[    5.558103] mmc0: Power save feature enable = 1
<6>[    5.558286] mmc0: DM non-cached buffer at ff418000, dma_addr 0x57932000
<6>[    5.558499] mmc0: DM cmd busaddr 0x57932000, cmdptr busaddr 0x57932300
<6>[    6.067837] mmc0: new high speed MMC card at address 0001
<6>[    6.069272] mmcblk0: mmc0:0001 KYL00M 14.6 GiB
~ # &#8592;[6n

 

[lepa71]

It's not just a data partition. I can't wipe system, data, either caches. It seems the whole emmc is corrupted.
So here is the output that shows emmc looks fine.

C:\Downloads\Droid\Rezound\tools>adb shell
~ # ←[6ndmesg | grep mmc0
dmesg | grep mmc0
<3>[    4.421384] mmc0: No card detect facilities available
<6>[    4.426999] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18
<6>[    4.428830] mmc0: Platform slot type: MMC
<6>[    4.432218] mmc0: 8 bit data mode enabled
<6>[    4.433927] mmc0: 4 bit data mode disabled
<6>[    4.436978] mmc0: polling status mode disabled
<6>[    4.438992] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[    4.448941] mmc0: Slot eject status = 0
<6>[    4.453885] mmc0: Power save feature enable = 1
<6>[    4.455655] mmc0: DM non-cached buffer at ff418000, dma_addr 0x57911000
<6>[    4.458737] mmc0: DM cmd busaddr 0x57911000, cmdptr busaddr 0x57911300
<6>[    4.890286] mmc0: new high speed MMC card at address 0001
<6>[    4.898801] mmcblk0: mmc0:0001 KYL00M 14.6 GiB
~ # &#8592;[6n

 

[scotty85]

Did you try "fastboot erase userdata" ?

After that, enter recovery and try:

Adb mount /userdata

Are you getting other partition errors as well,or just mmcblk0p35?

 

[lepa71]

fastboot erase userdata gets me this.

erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.008s

Do you want me fastboot boot recovery.mg or just reboot into recovery? I currently have TWRP latest installed.
I think all partition are screwed up.

 

[scotty85]

fastboot erase userdata gets me this.

erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.008s

Do you want me fastboot boot recovery.mg or just reboot into recovery? I currently have TWRP latest installed.
I think all partition are screwed up.

I'd try it both ways. But it prolly won't matter much if you use a booted or permantly installed recovery.

 

[lepa71]

What about other partitions? I can't mount them either.

 

[scotty85]

What about other partitions? I can't mount them either.

For now, we need to deal with the one that is giving you an error. Unfortunately, it does not look like there's much you can do without a signed ruu, and even that may not help.

Sorry to say it's not looking too good.

 

[lepa71]

I don't get it. I tried "adb mount /userdata" and got help printout for adb. Then I tried to this. See the output below

C:\Downloads\Droid\Rezound\tools>adb remount /userdata
remount failed: Success

C:\Downloads\Droid\Rezound\tools>adb shell
~ # ←[6nmount /userdata
mount /userdata
mount: can't find /userdata in /etc/fstab
~ # ←[6nll
ll
/sbin/sh: ll: not found
~ # ←[6nls
ls
and-sec              init                 sbin
boot                 init.rc              sdcard
cache                license              supersu
data                 mtdcache             sys
default.prop         nobrightness         system
dev                  proc                 tmp
emmc                 res                  ueventd.goldfish.rc
etc                  root                 ueventd.rc
~ # ←[6nls /cache
ls /cache
~ # ←[6nls
ls
and-sec              init                 sbin
boot                 init.rc              sdcard
cache                license              supersu
data                 mtdcache             sys
default.prop         nobrightness         system
dev                  proc                 tmp
emmc                 res                  ueventd.goldfish.rc
etc                  root                 ueventd.rc
~ # ←[6n

It looks like the folders structure is there. SO what can I do from shell? Can I repartition/format partitions(cache,data etc)?

In reality I need somehow s-off this phone so I can downgrade and run RUU on it. I believe this should fix my issues with internal storage, but on another note if ruu can do it why can't I do it with adb or fastboot.

Any other thoughts?

I really really appreciate you helping me out on this.

Thanks

 

[lepa71]

Just another thought.

I was playing with adb shell and push. I'm able to push files in the sdcard folder and data folder. May be the only thing is broken are the mount links to /emmc , /data , /cache etc. I can access folders with adb shell just fine.

What do you think?

Thanks

 

[scotty85]

I don't get it. I tried "adb mount /userdata" and got help printout for adb. Then I tried to this. See the output below
oops,i goofed that one up,should have been adb shell mount /userdata

but i see youve allready figured that one out good job.

i wonder if it cant mount userdata,becasue its gone? or i guess that mmcblk0p35 could be the userdata block for human identification,but to the phone is not actually called that. for what its worth,i just did a search on my one for "userdata" using root explorer,and it did not find it anywhere in the filesystem.

you might try and list what in /etc and /etc/fstab since thats where it seems to be looking for it.

C:\Downloads\Droid\Rezound\tools>adb remount /userdata
remount failed: Success

C:\Downloads\Droid\Rezound\tools>adb shell
~ # ←[6nmount /userdata
mount /userdata
mount: can't find /userdata in /etc/fstab
~ # ←[6nll
ll
/sbin/sh: ll: not found
~ # ←[6nls
ls
and-sec              init                 sbin
boot                 init.rc              sdcard
cache                license              supersu
data                 mtdcache             sys
default.prop         nobrightness         system
dev                  proc                 tmp
emmc                 res                  ueventd.goldfish.rc
etc                  root                 ueventd.rc
~ # ←[6nls /cache
ls /cache
~ # ←[6nls
ls
and-sec              init                 sbin
boot                 init.rc              sdcard
cache                license              supersu
data                 mtdcache             sys
default.prop         nobrightness         system
dev                  proc                 tmp
emmc                 res                  ueventd.goldfish.rc
etc                  root                 ueventd.rc
~ # ←[6n

It looks like the folders structure is there. SO what can I do from shell? Can I repartition/format partitions(cache,data etc)?
unfortunately,i dont think you cant do much with s on,and a normal ship hboot. you may actually need an eng hboot in order to format/repartition.

In reality I need somehow s-off this phone so I can downgrade and run RUU on it. I believe this should fix my issues with internal storage, but on another note if ruu can do it why can't I do it with adb or fastboot.
thats pretty much why i said an ruu may not help. there may be something goofed up somewhere an ruu isnt fixing. but then were back to being s on.. whatever the prollem is may be fixable with adb/fastboot given s off,and maybe an eng hboot.

Any other thoughts?

I really really appreciate you helping me out on this.

Thanks

i think for further s&g's,you should try booting a different recovery try fastboot booting the tried and true amon 3.15 listed in the root guide,and see if you still have the same errors and prollems. if for some reason you do not,you could at that point wipe and see if the phone will boot,and/or flash a different rom or restore a current backup.

Just another thought.

I was playing with adb shell and push. I'm able to push files in the sdcard folder and data folder. May be the only thing is broken are the mount links to /emmc , /data , /cache etc. I can access folders with adb shell just fine.

What do you think?

Thanks

hmm,thats possible. i think trying a different recovery may have an affect,if so. i would prolly keep booting it,as the booted recoovery may be able to acces partitions that the permanent recovery cannot,much like it is able to write the boot image.

something else you could try,is to whip yourself up a "miniruu" and flash that via hboot or fastboot. take an ruu,remove everything but boot,system,recovovery,and the android info text document.

now flash the main version low zip in recovery( xda-developers - View Single Post - HTC Misctool [Tool to read/write main version] )

leaving the bootloader unlocked, flash your zip. you can rename to PH98IMG and flash in hboot from the sd card,or flash in fastboot/ruu mode(how i would do it):

Spoiler

if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

if your 3 images flash successfully,try doing a factory reset and/or clear storage from hboot. since the stock recovery is able to "clense" areas of the phone that custom recoveries cannot,maybe that will get you up and running.

let me know if you need further explanations,i kept it short since you seem to have a pretty good idea what youre doing

 

[lepa71]

Hey. I was wondering if I can flash "setmainversion.zip" with fastboot flash zip file.zip. Do I have to do "fastboto oem rebootRUU" before it?

 

[scotty85]

Hey. I was wondering if I can flash "setmainversion.zip" with fastboot flash zip file.zip. Do I have to do "fastboto oem rebootRUU" before it?

no,the main version zip is not that type of file. it must be flashed in a custom recovery.

 

[lepa71]

I came back to say thank you. My rezound is officially dead. I tried everything I could, but now I got myself an S3. Rooted of course.

Thank you again for your help.

 

[scotty85]

I came back to say thank you. My rezound is officially dead. I tried everything I could, but now I got myself an S3. Rooted of course.

Thank you again for your help.

sorry for the late reply,been pretty crazy over the holiday. your quite welcome for the help,sorry we couldnt get it figured out. enjoy your new phone