[SOLVED] Missing "/dev/block/mmcblk0" - Vibrant Q&A, Help & Troubleshooting

Hi
I had the lastest stock ROM for my T-Mobile Samsung Vibrant with "DoW14 v1.4 344MB, Voodoo Lagfix, Sound, Color, BLN 2/21/2011". I had lag-fix applied as well as Voodoo sound. The phone had been working fine for months until a week ago when it didn't want to wake up. When I rebooted it started looping the first screen.
I have spend the last week trying to go back to stock with no luck. For some reason, my phone storage shows as "unavailable".
At this time I have in my phone Eugene's No Brick ROM with "3e" recovery applied as well as Overstock CWM recovery from CyagenMod Wiki (http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
My guess is that there is a problem with my internal SD card. I'm trying to follow the instructions in this post to try and format the internal memory but there is no "mmcblk0" in my "/dev/block/".
Here is the content of my "/dev/block":
Code:
# ls
stl5
stl2
stl1
bml11
bml10
bml9
bml8
bml7
bml6
bml5
bml4
bml3
bml2
bml1
bml0!c
tfsr12
tfsr11
tfsr10
tfsr9
tfsr8
tfsr7
tfsr6
tfsr5
tfsr4
tfsr3
tfsr2
tfsr1
tfsr0!c
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
bml12
stl12
stl11
stl10
stl9
stl8
stl7
stl6
stl4
stl3
ram0
Does it mean my internal SD memory is fried?
Sorry for the long email, but I am trying to give a good idea of my situation.
Still chasin

---

hmmm still no dice...
I was hoping someone would have chimed in by now. I still don't think my internal memory is fried, but I can't find where the internal memory is mapped. Even my "vold.fstab" file looks funny to me:
Code:
# cat vold.fstab
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1
## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# sdcard mount for the P1
# internal sdcard
{
mount_deep = 0
## [NAGSM_Android_HDLNC_SDcard_SeoJaeWoong_20101015 : do not use CD_ROM
# ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun0/file
asec = disable
mbr_policy = skip
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# externel sdcard
{
mount_deep = 1
## [NAGSM_Android_HDLNC_SDcard_SeoJaeWoong_20101015 : do not use CD_ROM
# ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun2/file
ums_path = /sys/devices/platform/s3c-usbgadget/gadget/lun1/file
asec = enable
mbr_policy = overwrite
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
See the following line:
Code:
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
There is no such locaton /devices/..." in my directory so why is this fstab points there????
At this point I'm still searching where the Eugene No Brick Rom got installed. Hopefully, once I find that out, I can reformat the drive and be able to install stock ROM.
chasin

---

Not one answer so far? I wonder if the developers and people in the know even read the Q & A forum.
Spend more time today and tried to follow this post: !SOLVED! Vibrant Internal Memory application storage 0b, please help! but it didn't help. After every ROM install I keep getting the same error message:
Code:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
No such file or directory
What confuses me is that any of these ROMs install at all if I'm having problem with my internal memory? Where are they being installed?
Help please!!! I have no more hair to pull
chasin away

---

Have you tried Odining?

---

I have had Dan_Brutal's original Vibrant at my house for the last few months, with this exact same problem. The only firmware, I have tried them all, that it will boot with is Eugene's JK2 package. I have it linked over in my RootzWiki ICZen thread, its worth a shot to flash it and see if it boots, however, when Dans boots up with that firmware, it reports a corrupt sd and is basically unusable.
I have done everything to this phone, flashed every firmware out there, tried repartitioning in recovery, even built custom Heimdall and Odin packages that work fine on mine, nothing will boot. I also tried the reparted technique, which is worth looking into, you might have better success with it. You can follow the reparted steps, but using the Vibrant specific partition structure, and it might work. It didn't on Dan's, I ran it and matched my partitions, and nothing.
If you need the stock partition mapping, let me know and I'll dig it up for you. Its probably faster to contact me on RW, I'm not over here very much anymore. And you are right, we rarely read Q&A, lol.
Sent from my ICZen Experience

---

Br1cK'd said:
I have had Dan_Brutal's original Vibrant at my house for the last few months, with this exact same problem. The only firmware, I have tried them all, that it will boot with is Eugene's JK2 package. I have it linked over in my RootzWiki ICZen thread, its worth a shot to flash it and see if it boots, however, when Dans boots up with that firmware, it reports a corrupt sd and is basically unusable.
I have done everything to this phone, flashed every firmware out there, tried repartitioning in recovery, even built custom Heimdall and Odin packages that work fine on mine, nothing will boot. I also tried the reparted technique, which is worth looking into, you might have better success with it. You can follow the reparted steps, but using the Vibrant specific partition structure, and it might work. It didn't on Dan's, I ran it and matched my partitions, and nothing.
If you need the stock partition mapping, let me know and I'll dig it up for you. Its probably faster to contact me on RW, I'm not over here very much anymore. And you are right, we rarely read Q&A, lol.
Sent from my ICZen Experience
Click to expand...
Click to collapse
Thanks for taking time to reply. My only two options are to try and use an external SD card or return ti to Samsung for repair. It pains me to say it, but I'm going to try and return it to Samsung and see how much they will charge me to fix it. I have already spend over 30 hours trying to fix this thing.
If Samsung wants and arm and a leg to fix it, I will probably got back to your idea of partitioning an external SD card and use that as phone's internal memory.
Thanks chasin
P.S. I'll keep the thread going for a few more weeks until I come to a solution.

---

Im wondering what's the difference of this error with the "Encryption Error" bug...
My phones internal sd is inacessible bacause of Encryption Bug that's said to be coming from early ICS Roms. Right now im running on a fix, using the external sd. The fix is posted here in Q & A.
Nice seeing you here Br1cK'd!
I know u can't resist to help.
Luv your IC Zen 1.7

---

gshmod known
silvercrown266 said:
Im wondering what's the difference of this error with the "Encryption Error" bug...
My phones internal sd is inacessible bacause of Encryption Bug that's said to be coming from early ICS Roms. Right now im running on a fix, using the external sd. The fix is posted here in Q & A.
Nice seeing you here Br1cK'd!
I know u can't resist to help.
Luv your IC Zen 1.7
Click to expand...
Click to collapse
The symptoms may be the same (unusable internal memory) but the cause is different. I was running Froyo not ICS when the problem started and I never got the encryption error.
I guess at the end of the day, the basic question I was rying to find was:
Is there a way to test the internal memory and determine if it is faulty?
If Eugene No Brick Rom is installed, where is being installed if the internal memory is bad?
If Samsung is asking too much money to fix my phone, by backup plan is to use the external card.
Thanks chasin

---

Here is an update to the thread. I just checked Samsung repair status and it saus the following:
Code:
*05/16/2012//11:38:50//0001773863//Telephone//ASC*
2012-05-16 ?? 10:38-JaeSung Ko: The unit has left the technician. SOLUTION: Replaced PBA
Looks like they had to replace the main board on the phone. I hope that means I was right and it was a hardware problem. Although I wished there was a way to test that. Hopefully I'll get my phone next week and close this thread.
chasin
P.S. I need to figure out how to update the a thread as solved when I'm done.

---

Solved
I finally got my phone from Samsung and they did replace the mainboard on the phone. I would like to think that it confirmed my suspicions that it was a hardware problem, not just a software corruption.
Total cost it was about $70 which included shipping both ways and part replacement. This was a pleasant surprise, considering the phone was out of warranty. It makes me feel good about my decision to skip those phone protection plans (which have a $50 deductible and ~$5 a month), but I'm usually careful with my phones.