[Vibrant Q&A, Help & Troubleshooting] fagnerkof:
Updating info

I have here 3 Odin Flasheable Roms that I've tried to restore my Vibrant with, but in no one of them I can access internal or external sd:

STOCK T959UVJFD.tar

Eugene_2E_JK2_Froyo

lidroid-sgs-2.4.0-t959

When flashing any of that roms on odin, it passes and get no error, but I got the results:

STOCK T959UVJFD.tar - Cell stuck on vibrant logo bootloop, can't boot, doesn't have recovery menu

Eugene_2E_JK2_Froyo - Boots the cell (can dial etc) - have a very limited recovery menu and that I can't parted in adb shell or other commands.

lidroid-sgs-2.4.0-t959 - Stuck on bootloop, but have CWM Recovery v3.0.2.4, with all the default options of a CWM and when adb'ing allow me to use shell commands like parted etc.

So, in adb shell with the lidroid I cast fdisk and got:

# fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Unknown value(s) for: cylinders (settable in the extra functions menu)

Disk /dev/block/mmcblk0: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1 0 0 Empty
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 0) logical=(0, 0, 1)
Partition 1 has different physical/logical endings:
phys=(0, 0, 0) logical=(267349, 89, 4)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 1 1 0 0 Empty
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 0) logical=(0, 0, 1)
Partition 2 has different physical/logical endings:
phys=(0, 0, 0) logical=(267349, 89, 4)
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 * 1 1 0 0 Empty
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 0) logical=(0, 0, 1)
Partition 3 has different physical/logical endings:
phys=(0, 0, 0) logical=(267349, 89, 4)
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 * 1 1 0 0 Empty
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 0) logical=(0, 0, 1)
Partition 4 has different physical/logical endings:
phys=(0, 0, 0) logical=(267349, 89, 4)
Partition 4 does not end on cylinder boundary

Try using parted also get me errors like

# parted
parted
Error: No device found
Retry/Cancel? c

# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
Error: Error opening /dev/block/mmcblk0: Invalid argument

and

# mount /dev/block/mmcblk0
mount /dev/block/mmcblk0
mount: can't find /dev/block/mmcblk0 in /etc/fstab
# mount /dev/block/mmcblk0p1
mount /dev/block/mmcblk0p1
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory

I can even move files to internal sd using push, like

C:\android-sdk-windows\platform-tools>adb push update.zip /sdcard
1779 KB/s (1804447 bytes in 0.990s)
C:\android-sdk-windows\platform-tools>

but still can't mount or make partitions. Thus I moved an update.zip to use in the recovery menu (apply update from sdcard), and when I do it even reads and run the update.zip, but it says "E: can't mount /sdcard/update.zip > Installation aborted". I'm afraid that in that case its using only a temporary memory (ram, cache, I don't know for sure) and I will not have access to sd.

I can list files in these directories (even /dev/block/mmcblk0) but can't mount, format or make partitions... What I want to know is if is there any other way to fix this internal sd.

More info:

Command fat.format gives

# fat.format /dev/block/mmcblk0p1
fat.format /dev/block/mmcblk0p1
fat_init_volume[149]: Check here: No such file or directory

Fail to format
# fat.format /dev/block/mmcblk0p2
fat.format /dev/block/mmcblk0p2
fat_init_volume[149]: Check here: No such file or directory

Fail to format
# fat.format /dev/block/mmcblk0
fat.format /dev/block/mmcblk0
Success to format

and busybox:

# busybox mount
busybox mount
rootfs on / type rootfs (rw,relatime)
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/stl6 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
/dev/block/stl9 on /system type rfs (rw,relatime,vfat,llw,check=no,gid/uid/rwx,i
ocharset=utf8)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/stl11 on /cache type rfs (rw,nodev,noatime,nodiratime,vfat,llw,gid/ui
d/rwx,iocharset=utf8)

# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 164.6M 164.6M 0 100% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 164.6M 8.0K 164.6M 0% /tmp
/dev/block/stl9 275.8M 252.4M 23.4M 92% /system
/dev/block/stl11 30.1M 20.0K 30.0M 0% /cache