yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] upbeat.addict:
Are certain that yr referring to the correct path? "/dev/block/stl9" for me is mounted fine and is indentified as "/system". I even did just a quick dump of it and compared it to the factoryfs.rfs of the last rom i flash and it's relatively identical. The mount points for all the SD cards are on "/dev/block/mmc*" paths, since both the internal and external SD are accessible by the mmc interface.

If I can't successfully mount the internal SD, but the external seems to be fine, which i've been able to access via usb as well, then I assume it would be possible to partition an external sd card and create the 3(4?) partitions needed by android to function properly. its a inconvenient fix, but as a developer, i've put up with my share of hacky work-arounds.

one thing that strikes me as unusual is that when i put in my external sd card, the mounting points appear in both the "/devices/platform/s3c-sdhci.#" "/dev/block/vold/" paths for some reason. i'm not sure why the external sd card is being represented twice or shows up as 2 separate volumes.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
no i am not :-) It was a mistake it should be /dev/block/mmcblk0p2
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
UVKB1-Heimdal

Only Eugene's JK2 had sbl and bootlaoder. I pulled everything from my Vibrant

if anyone wants to give it a try, download from http://www.megaupload.com/?d=6JSYXPCB

It is not an ODIN'able tar archive, but you will need to flash using Heimdall with repartition, and if your phone boots up, then do a factory reset from settings. The dbdata.rfs has all the garbage from my phone, I did not do factory reset before making the files, otherwise I had to spend an hour to re-do my phone.

I am not sure it will help, but you never know. This is UVKB1 with recent sbl and boootloader. If luckily someone reports success, we can make ODIN'able tar file later.
[Vibrant Q&A, Help & Troubleshooting] zentronic:
funny thing i lost my phone lol oh well guess ebay found it and im doing the replacement well worth the 5 bucks a month.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
disappeared in the air out of blue? That is called invisible brick :-)
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Ssiddiqi1:

thank you for all your help brotha. Off and ON the forum. I will try this later today and I will let you know.

Cheers
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Has anyone tried to put this in .tar format and see if it works. Heres the link http://xdaforums.com/showthread.php?t=846384
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Those are only two vold files. They are already in Eugene JK2. Even with those vold files external sd card was still showing up as a 2 GB card regardless of its actual size. Samsung corrected the bug in later releases starting from JK4. the KB1 I posted has the issue corrected. vold conf files will not help you in your case. It is mount problem due to corrupted sectors on /data partition.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
How about the Aio toolbox, if not that then why wont someone notify morfic or another dev to try and help us.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
What is with AIO Toolbox? Do you mean flashing KB1 files I posted? if so, I have no idea if AIO toolbox can do it. Heimdall certainly can do flash with repartition.

Allen posted Morfic already knows about it. SamVib Vibrant was bricked too, as he posted on one of the thread. He replaced it, therefore I assume TeamWhiskey knows it too. More than that I don't know, if any dev is trying to figure out a fix.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
Somehow I at least feel less lonely.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
That is a good thing :-)
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Here is what aio toolbox has http://xdaforums.com/showthread.php?t=954509
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
If you are not comfortable with Heimdall, I made ODIN'able tar for you. Here is the link http://www.megaupload.com/?d=FW5AWT7B

use it with a pit512 and repartition checked to flash. It is UVKB1 with recent boot loader and sbl.bin as posted before.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
I know the link, but is not AIO toolbox just a user interface to start ODIN and flash UVJFD etc etc, which you already had done?
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
No its not that but I was thinking maybe it would work better because the flash back to stock option starts odin one click, which we havent attemted yet. Does the file of uvkb1 boot up and does it work and/or fix the problem
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
Hey Ssiddiqi1:

Thank you. I loaded this up with ODIN. The phone boots. But I get the blank screen. It's on- but it's having trouble loading the OS.

So, unlike JK2- Froyo, where I could boot into home and use the phone. Now, KB1 doesn't boot into the OS.

Thanks anyway man. This phone is toast. I'm going to throw it under the car and burn rubber with it.

*sigh*

-Frustrated.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
It was just a try. Eugene JK2 has different file system, it will boot you. The KB1 I uploaded is a full KB1, if it does not boot to home screen then phone is a toast.

We are coming to that conclusion this morning. As I said, it has fried internal sd card like Bell Canada cases. :-(
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
NO guarantee, it will fix the problem. It is something to try, you can always revert to Eugene JK2 to boot the phone.

You can try AIO toolbox, but results maybe same as you had with odin'ing UVJFD.

I am running out of solutions, as everyone else. One thing for sure, internal sd card 14 GB partition for data had been fried completely.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I just gave it a try too. Only I didn't have repartition checked. I had the same results as the member above. I even tried using recovery to format the sdcard.

I also found that I couldn't access the phone with ADB shell either. That's when it was in recovery and while it was booting. It doesn't even show on adb devices or in Device Manager for that matter.
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
I hear ya brotha.

Thank you for all your help though.

you put way more time in this than I would expect from anybody.

Not to worry. This thing is toast.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Obviously, you cannot use UI menu to format. That is a crap from Samsung, if phone does not boot, how one can use UI menu to format? :-)

Your errors confirm the belief that internal 14 GB /data partition is inaccessible, not repartition-able, it is fried. Well, maybe you call TMO if you bought your phone from TMO and get it replace, flash the UVJFD before sending it back.

I am out of solutions now, though we know what exactly the problem is, which we cannot fix.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Thanks a lot

Last idea came to my mind, make a odin'able KB1 with sbl, bootloader and voodoo enabled, may Linda from voodoo could re-write data partition when it tried convert /data to ext4.

But this can happen only tomorrow as I am off to bed now.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I miss Linda. Come back to me Linda! I'll never mess around with other kernels again! I promise!
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
If the phone hangs around the set partition part for a pretty long time, then is that a good thing or a bad thing?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Could be both. If something is missing in OS then it is good because it can be fixed. A bad partition can also cause to hang because something cannot mount, then bad, which seems to be in these cases.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
EDIT Linked REMOVED see post 301

As before, I did not factory reset my phone therefore dbdata is hugewith garbage from my phone. If luckily phone boots up, and Linda does her job, then do a factory reset from Settings.

This is last idea I had. You can flash Eugene JK2 in case phone does not boot and use only for making/receiving calls or exchange...................
[Vibrant Q&A, Help & Troubleshooting] manjish:
oh oh

i am in the same boat..........as many here.......dow gave boot loop and after that i cannot mount the internal and external sd.....no rom can boot the phone except Eugene_2E_JK2_Froyo.......but no sdcard mounted...

now that since its almost certain that its not easily fixable......could it be possible to just sym link external sd as sdcard.........that way phone will be back to 99% functional........im not software guy so not much idea on how but i know its possible......EXPERTS !!!! HELP!!

i also heard something about PARTED in cyanogenmod forum.....could that be used to format the 14 gb sdcard partition??

i cannot repair or replace the phone as im not from USA..

save us symlink ......

also any words from the devs../???
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
You cannot symlink an external sdcard to internal sdcard. Beside os is not working completely, it is refusing to mount internal sdcard, therefore further hacking on such phones is not easy.

Try the UVKB1 with voodoo I just posted, ODIN it with a 512 and repartition checked. If boots ok, it may take time to boot since voodoo is enabled, if it does not boot you can odin eugene JK2 again.

are you from India? I believe there is Samsung service center in Delhi, or Hydrabad, check their web site for info.
[Vibrant Q&A, Help & Troubleshooting] wtf.now?:
Has anybody figure out why is this happening?

Had they contact the kernel developer and most importantly had they pull out the kernel offline to prevent this from spreading further.
[Vibrant Q&A, Help & Troubleshooting] manjish:
oh thats very sad....are you sure?? .,,,, but still i have hope for it

also im from nepal.....near india.......

will a service centre in india repair tmobile vibrant t959 as they dont sell them....(as they sell international galaxy s i9000).....

also can i repair it paying to service centre in USA........i can arrange to send it to USA for repair.....but i dont have warranty or anything.....

but still i want to try everything possible........any news on parted

:confused::confused:
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
i do not know if Indian office will fix US variants. YOu can call and check

send to US and have it fixed? In that much money you can buy a new one.

parted will not help.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
It starts to boot up but just sits at the black screen. The buttons on the button work (light up but don't turn back off). I'll let it sit for a few minutes just for the hell of it. For some reason I can't access it through ADB either so I have no idea what's going on.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
You cant connect ADB because USB Debugging is off

Anyway, I am making a final ODIN'able tar file with sdparted, voodoo and USB debugging on. It should be ready in an hour. After flashing you need to get into recovery via adb reboot recovery, then advance and use partition and format options to use sdparted. If that cant rescue, all hopes are a waste.

Just hangin, as soon as I finish it and upload it, I will post a link.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
Staying hopeful.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
OK, here it is:

http://www.megaupload.com/?d=54WGIP8S

It has recovery from ClockWork and voodoo kernel, USB Debug enables so hopefully adb will connect, the sdparted files are already in factoryfs.rfs

after ODin,ing, try to get into Recovery, preferably by adb reboot recovery command

if you get into recovery, go to advance, clear cache, and then use format and repartition to use

Hopefully it helps. I do not have a bricked phone like all of you, therefore i cannot fully test.

If this cannot rescue, then I am now completely out of ideas

Good luck

as usually, you can always flash back to Eugene JK2 if it does not work
[Vibrant Q&A, Help & Troubleshooting] nate420:
vibrants are tanks..... ive had hardware brick... confimed by tmobile still got it unbricked with a jig... try everything... and always odin before flashing other roms even if the dev. says you can flash over so-n-so rom... just to be sure any lingering data is left from other roms
[Vibrant Q&A, Help & Troubleshooting] upbeat.addict:
gave it a shot, no go. it just sat at the vibrant logo for me. after i flashed the factoryfs.rfs from the JK2, i could finally boot, but i think it removed the clockworkmod recovery...unless im mistaken, but isn't that just a binary stored under /system ? it would at least explain why i didn't see it on reboot. I have had the option to wipe internal sd from the recovery screen in previous flashes i've done, but it never mattered because the phone can't mount the sd anywho. sure, it'll say it's wiping and even say it's completed, but it does it in a matter of 1 second and just ends. no errors, no nothing. but once you reboot, nothing's changed.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
factoryfs.rfs from JK2 will remove the clockwork recovery. Were you not able to connect adb, even at Vibrant logo? clockwrok recovery is stored in /system/bin

This one has voodoo enabled by default also, so Linda could rewrite partitions.

since sd card is not mounting, it is sitting at vibrant logo.

well, these were final ideas i.e. package clockwork recovery, sdparted and voodoo in the ODIN'able tar. I am out of ideas now.

EDIT: Can you boot into Recovery with JK2 and see install package option?
[Vibrant Q&A, Help & Troubleshooting] upbeat.addict:
i wasn't achieving adb access after i flashed it and it sat at the logo. And no, since i reflashed JK2, the only options are the wipe userdata/cache, reinstall packages and reboot. i'm just stabbing in the dark here with what i can loosely make out about the mmc controller device that controls the internal/external sd. since you mentioned you were not experiencing the same issues as us, as long as yr not running a I9000 setup, then the results of this command should be the same. If you can, pulled the external and run the command again to notice the differences:

find / -name *mmc*

/sys/devices/platform/s3c-sdhci.0/mmc_host

/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0

/sys/devices/platform/s3c-sdhci.1/mmc_host

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1/mmc1:0001

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:1

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:2

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:3

/sys/devices/platform/s3c-sdhci.2/mmc_host

/sys/devices/platform/s3c-sdhci.2/mmc_host/mmc2

/sys/bus/mmc

/sys/bus/mmc/devices/mmc1:0001

/sys/bus/mmc/drivers/mmcblk

/sys/bus/sdio/devices/mmc1:0001:1

/sys/bus/sdio/devices/mmc1:0001:2

/sys/bus/sdio/devices/mmc1:0001:3

/sys/bus/sdio/drivers/bcmsdh_sdmmc

/sys/bus/sdio/drivers/bcmsdh_sdmmc/mmc1:0001:1

/sys/bus/sdio/drivers/bcmsdh_sdmmc/mmc1:0001:2

/sys/bus/sdio/drivers/bcmsdh_sdmmc/mmc1:0001:3

/sys/class/mmc_host

/sys/class/mmc_host/mmc0

/sys/class/mmc_host/mmc1

/sys/class/mmc_host/mmc2

/proc/irq/180/bcmsdh_sdmmc

/proc/irq/188/mmc2

/proc/irq/92/mmc2

/proc/irq/91/mmc1

/proc/irq/90/mmc0

can you try this out on yr phone and post the result. I have a feeling that the setup has been targeting the wrong path the entire time, why this would continue to affect the numerous other roms i've flashed is beyond me, but in the configs, the device labeled mmc0 has generally been referring to the internal sd (except in i9000), yet currently my phone is identifying a device on mmc1 and it appears to have 3 partitions and I've had my external sd pulled from my phone for days now. im just curious about it. thanks again for all yr help. im willing to try anything you come up with as well, packaging a CWM for flashing thru Odin sounds like a good idea. Would simply "pushing" the binary into place work as well? Because file manipulation is a walk in the park at this point.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I just gave it a try and it just sat at vibrant screen. I couldn't get it into recovery either and couldn't access it through adb.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Mine has more devices. Here it is

# find / -name *mmc*

find / -name *mmc*

/sys/fs/ext4/mmcblk0p2

/sys/devices/platform/s3c-sdhci.0/mmc_host

/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0

/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001

/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0

/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p

1

/sys/devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0/mmcblk0p

2

/sys/devices/platform/s3c-sdhci.1/mmc_host

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1/mmc1:0001

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:1

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:2

/sys/devices/platform/s3c-sdhci.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:3

/sys/devices/platform/s3c-sdhci.2/mmc_host

/sys/devices/platform/s3c-sdhci.2/mmc_host/mmc2

/sys/devices/platform/s3c-sdhci.2/mmc_host/mmc2/mmc2:adbb

/sys/devices/platform/s3c-sdhci.2/mmc_host/mmc2/mmc2:adbb/block/mmcblk1

/sys/devices/platform/s3c-sdhci.2/mmc_host/mmc2/mmc2:adbb/block/mmcblk1/mmcblk1p

1

/sys/bus/mmc

/sys/bus/mmc/devices/mmc0:0001

/sys/bus/mmc/devices/mmc2:adbb

/sys/bus/mmc/devices/mmc1:0001

/sys/bus/mmc/drivers/mmcblk

/sys/bus/mmc/drivers/mmcblk/mmc0:0001

/sys/bus/mmc/drivers/mmcblk/mmc2:adbb

/sys/bus/sdio/devices/mmc1:0001:1

/sys/bus/sdio/devices/mmc1:0001:2

/sys/bus/sdio/devices/mmc1:0001:3

/sys/bus/sdio/drivers/bcmsdh_sdmmc

/sys/bus/sdio/drivers/bcmsdh_sdmmc/mmc1:0001:1

/sys/bus/sdio/drivers/bcmsdh_sdmmc/mmc1:0001:2

/sys/bus/sdio/drivers/bcmsdh_sdmmc/mmc1:0001:3

/sys/class/block/mmcblk0

/sys/class/block/mmcblk0p1

/sys/class/block/mmcblk0p2

/sys/class/block/mmcblk1

/sys/class/block/mmcblk1p1

/sys/class/mmc_host

/sys/class/mmc_host/mmc0

/sys/class/mmc_host/mmc1

/sys/class/mmc_host/mmc2

/sys/block/mmcblk0

/sys/block/mmcblk1

/dev/block/mmcblk1p1

/dev/block/mmcblk1

/dev/block/mmcblk0p2

/dev/block/mmcblk0p1

/dev/block/mmcblk0

/proc/irq/180/bcmsdh_sdmmc

/proc/irq/188/mmc2

/proc/irq/92/mmc2

/proc/irq/91/mmc1

/proc/irq/90/mmc0

/proc/fs/ext4/mmcblk0p2

/proc/fs/jbd2/mmcblk0p2-8

#
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
here is link for CWM Recovery ODIN , I can try to make it if you want?

http://xdaforums.com/showthread.php?t=823089#8904406
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
This one wouldn't work?

http://xdaforums.com/showthread.php?t=942021
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
that is a reference on how, which is helpful on how to get recovery.bin out from a working Vibrant. cat /proc/partitions on my vibrant

major minor #blocks name

137 1 256 bml1

137 2 256 bml2

137 3 10240 bml3

137 4 1280 bml4

137 5 1280 bml5

137 6 5120 bml6

137 7 7680 bml7

137 8 7680 bml8
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
that is what it is from dd if=/dev/block/bml8 of=/sdcard/recovery.bin bs=4096

but from fascinate

better to pull from a Vibrant to be safe, since bml7 and bml8 both have same blocks and kernel images too
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
CWM Recovery from Vibrant ODIN'able Here it is

good luck

http://www.megaupload.com/?d=O1AX8ALI
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I must've done something wrong because it's not working. I still have Android system recovery <2e>

I used the Phone checkbox. Is that the correct one?

I tried PDA and got this:
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
from adb can you do

adb shell

su

cat /proc/partitions

and post the out put.

You can give the fascinate one from link you posted a try, and see what it does? maximum, you may have to reflash JK2
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
# cat /proc/partitions

cat /proc/partitions

major minor #blocks name

139 0 513024 tfsr0/c

139 1 256 tfsr1

139 2 256 tfsr2

139 3 10240 tfsr3

139 4 1280 tfsr4

139 5 1280 tfsr5

139 6 5120 tfsr6

139 7 7680 tfsr7

139 8 7680 tfsr8

139 9 293376 tfsr9

139 10 137216 tfsr10

139 11 35840 tfsr11

139 12 12800 tfsr12

137 0 513024 bml0/c

137 1 256 bml1

137 2 256 bml2

137 3 10240 bml3

137 4 1280 bml4

137 5 1280 bml5

137 6 5120 bml6

137 7 7680 bml7

137 8 7680 bml8

137 9 293376 bml9

137 10 137216 bml10

137 11 35840 bml11

137 12 12800 bml12

138 3 6400 stl3

138 6 1280 stl6

138 9 284672 stl9

138 10 131584 stl10

138 11 32000 stl11

#
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
bml8 is there,

well give the one from the link you posted a try
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
Still with Android system recovery <2e>

# cat /proc/partitions

cat /proc/partitions

major minor #blocks name

139 0 513024 tfsr0/c

139 1 256 tfsr1

139 2 256 tfsr2

139 3 10240 tfsr3

139 4 1280 tfsr4

139 5 1280 tfsr5

139 6 5120 tfsr6

139 7 7680 tfsr7

139 8 7680 tfsr8

139 9 293376 tfsr9

139 10 137216 tfsr10

139 11 35840 tfsr11

139 12 12800 tfsr12

137 0 513024 bml0/c

137 1 256 bml1

137 2 256 bml2

137 3 10240 bml3

137 4 1280 bml4

137 5 1280 bml5

137 6 5120 bml6

137 7 7680 bml7

137 8 7680 bml8

137 9 293376 bml9

137 10 137216 bml10

137 11 35840 bml11

137 12 12800 bml12

138 3 6400 stl3

138 6 1280 stl6

138 9 284672 stl9

138 10 131584 stl10

138 11 32000 stl11

#
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
The system is not allowing to read/write anything

if you have install package in 2e recovery, you can try attached update.zip, but I am sure it will fail to due to read/write problems
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I don't have sdcard access. :(
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
adb push does not work? if so, trouble trouble....
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I unzipped the update.zip and tried to adb push the sbin

push: sbin/tune2fs -> /sbin/tune2fs

failed to copy 'sbin/tune2fs' to '/sbin/tune2fs': Permission denied
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
well that is due to mount problem, the internal sd is fried.

this is very drastic and could be brute force repartition

attached is pit file with ext4 partition table from Vibrant

ODIN Eugene JK2 with this pit file and repartition checked

your phone may not boot and hang at Vibrant logo since Eugene is not ext4, but if starts recognizing internal sd card, you can use pit512 to repartition and could be back in business. This is a brute force, do it only if you feel comfortable.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Let me know if that method works and if it does, then please give me the instructions on what you did exactly. One question, will Jtag repair work to fix this problem, if you dont know what I am talking about then search it on youtube.
[Vibrant Q&A, Help & Troubleshooting] Henchman:
Try mounting in rw mode.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Jtag for getting phones into Download if you cannot get them into Download. In your case it will not help. You are able to get into Download so it is not needed.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
I believe other had tried through adb shell, and get permission denied

you can try adb remount
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
ODIN is sticking on

<ID:0/006> Added!!

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> Enter CS for MD5..

<ID:0/006> Leave CS..

<ID:0/006> Set PIT file..

<ID:0/006> DO NOT TURN OFF TARGET!!

and won't change. Advice?
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
Half hour later and still the same.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
It wouldn't repartition with that pit file. I left it on ODIN for over an hour and it did nothing. :(