yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Excuse me dear, why are you using Eugene JK2? Eugene's JK2 is not Froyo-that-does-not-brick. Eugene's Froyo-that-does-not-brick is compiled from JPX-1900 (International Vibrant version.) You need Eugene373_GalaxyS_Froyo_PDA.tar from http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8.

Eugene had Instructions on the above link, on how to flash it. After boot you will see your phone will report 1900. Let phone sit for 10 min after boot then get into download mode and Odin UVJFD with pit512 and repartition checked.

EDIT: Eugene JK2 does not have necessary data file which are present in JFD. You can try to get into download (hold volume +/-, start ODIN, connect USB to PC then to phone while holding volume +/- buttons - it will get you into download) Try ODining UVJFD/pit512 with repartition checked. Maybe it will save you trouble of flashing Eugene373_GalaxyS_Froyo_PDA.tar.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Reformat = repartition
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I dont have adb installed
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
You do not need adb, ignore those instructions from Eugene website. Those instructions are useful if you plan to use froyo-that-does-not-brick for a longer drive. Your purpose is to fix the phone, then revert to UVJFD followed by flashing another stock Froyo ROM of your choice. {{I use stock UVKB1 (whitehaux Deodexed stock version, with supercurio's KB1+voodoo) with root.}}

EDIT: It is always good to have adb installed if you are playing with various ROMs. It come handy to get into download or recovery in case phone is messed-up. Heimdall comes handy too if you ever get stuck at the screen of death with pc--!--phone icon.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I tried flashing Eugenes no brick and I still cant get past the recovery 3e screen and I cannot select an option
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
IS phone booting and going into 3e recovery?

pull the battery

put the battery back after a few second

start ODIN

connect USB to PC, but not to phone

hold the volume +/- key

connect USB to phone while holding vol +/- keys

Your phone should be in Download mode now

load pit 512 in ODIN

load UVJFD.tar in PDA

check repartition

and hit Start on ODIN

when finished

let phone boot fully, then let it sit for 10 minutes

then reroot etc etc
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
The phone is booting and going into recovery 3e but i am going to try your method and see if it works.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
/dev/block/mmcblk0p2 should mount to /data to do anything else.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Which kernel messed up your phone? DOW?

How did you get parted working?

Have you tried ODining UVJFD with a pit512 and repartition? If your /data is mounting to /dev/block/mmcblk0p2 then your internal sd is ok, you should be able to flash UVJFD with a pit512, repartition and then boot root and flash a foryo latest release.

factory.rfs is most of firmware except kernel, dbdata is usually not needed, so cache.rfs is also not needed. The new ROM flashes usually do not touch primary boot loader and sbl, but seems to me OC kernel crash messed boot loaders, therefore those are needed.
[Vibrant Q&A, Help & Troubleshooting] tekowalsky:
Yes, I was using DOW. The very first thing I tried was to Odin to UVJFD with pit512. I also tried it with the repartition. I tried Eugene's with the repartition as well, etc., etc.

To get parted working I ODINed to the weird combination of Eugene's JK2, JK6, and the voodoo kernel. I connected adb in normal phone mode. I used SuperOneClick to get shell root. I remounted /system as rw. I pushed parted to /system/bin then did chmod 755 on parted.

My mmcblk0p2 is not my internal SD. Yes, I know it SHOULD be my internal SD but it isn't. I had an 8GB external SD in my phone.

mmcblk0 was reporting as 8 GB and not 16 GB. mmcblk0 was reporting two partitions (2GB and 6GB). The 2GB was mmcblk0p2 and mounting as /data

I ran a test. I removed my external SD and tried to boot up my phone. Kernel Panic. Tried it again - same. I put a 4GB SD in the external slot. My phone booted okay.

I connected ADB, SuperOneClick to Shell Root, and ran "parted /dev/block/mmcblk0". parted reported the size of mmcblk0 as 4 GB. The /data partition is on the external SD.

In my list of /dev/block I should see mmcblk0 and mmcblk1. I don't -- just mmcblk0.

I'm trying to find a mount listing of a stock system but I think this is the way /data is supposed to be mounted (external SD). Just the external SD is supposed to be mmcblk1 and NOT mmcblk0 (I think...)

:(
[Vibrant Q&A, Help & Troubleshooting] maxdiesel215:
In my case, I am able to load applications from the market but I am on Eclair instead of Froyo. I have called T-mobile and requested a replacement because any time I try to update to Froyo I lose my ability to add apps. Also as I said it shows that I am not able to mount an external sd.
[Vibrant Q&A, Help & Troubleshooting] tekowalsky:
partitions

I believe Eugene's JK2 works for us because it repalces both boot loaders.

The only part it doesn't replace if you use Heimdahl is "Recovery".

Forgot to mention I ODINed my weird combo (JK2/JK6/voodoo kernel) WITHOUT the PIT file.
[Vibrant Q&A, Help & Troubleshooting] tekowalsky:
pre-crash mount table

I found a copy I had made of my mount table about a week ago (before my phone crashed). /data was mounted the same then as now.

My internal SD card was at /dev/block/vold/179:9 -- 179:9 isn't in /dev/block/vold on my phone now.

Also possibly relevant to our situation and a good read!!!

http://xdaforums.com/showthread.php?t=957284

rootfs / rootfs rw,relatime 0 0

proc /proc proc rw,noatime,nodiratime 0 0

sys /sys sysfs rw,noatime,nodiratime 0 0

/dev/block/stl9 /system ext4 rw,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc 0 0

/dev/block/stl11 /cache ext4 rw,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc 0 0

/dev/block/stl10 /dbdata ext4 rw,noatime,nodiratime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0

/dev/block/mmcblk0p2 /data ext4 rw,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0

tmpfs /dev tmpfs rw,noatime,nodiratime,mode=755 0 0

devpts /dev/pts devpts rw,noatime,nodiratime,mode=600 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

/dev/block/stl6 /mnt/.lfs j4fs rw,noatime,nodiratime 0 0

tmpfs /mnt/asec tmpfs rw,noatime,nodiratime,mode=755,gid=1000 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/block/stl3 /efs rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0

/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0

/dev/block/dm-0 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/dm-1 /mnt/asec/com.rovio.angrybirdsseasons-1 vfat ro,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/dm-2 /mnt/asec/com.agilesoftresource-1 vfat ro,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/dm-3 /mnt/asec/com.aldiko.android-1 vfat ro,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
according to the link you posted efs.rfs back up could be your solution? Your efs from your mount table is same as any other vibrant. I posted efs.rfs in this thread a couple of days ago. You can look at it?
[Vibrant Q&A, Help & Troubleshooting] tekowalsky:
mmcblk1 = internal SD

Yes, I know my internal SD is inaccessible... :)

but no I did not partition my external SD card.

As both your posting and my own show /data is at mmcblk0p2. That directory is stored on the external SD. (And now that I think about it I remember being perplexed by this same issue the first time I upgraded the external SD card in my phone -- /data stored on the external SD.)

The information you posted in the stock /dev listing showed mmcblk1 -- that doesn't exist on my vibrant now. I suspect that is the internal SD.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
actually this is what /data on Vibrants as a 14 GB partition

/dev/block/mmcblk0p2 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_allo

c 0 0
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
Is it too much to ask for someone to create an odin flashable rom with the external sd card workaround? That way some of us can have an option. I'm so lost in this thread I don't know what to flash to make it work. :rolleyes:
[Vibrant Q&A, Help & Troubleshooting] tekowalsky:
I'm done. I've burned through 3 1/2 days of doing almost nothing but working this issue. I'm not a mobile phone savant but I'm not a complete slouch at troubleshooting either.

The internal SD device is genuinely not recognized by the phone. When the phone boots up it creates the device nodes for the external SD but completely ignores the internal MMC SD.

If the internal SD hasn't been turned "off" or crisped, well, who knows...

Many thanks to those who have taken this issue seriously.
[Vibrant Q&A, Help & Troubleshooting] :
Here try this, he's found a workaround. Good luck.

http://xdaforums.com/showthread.php?t=971575
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
Yeah, I already know about this. What I'm asking is if we can get this included in a rom that can be flashed via Odin.
[Vibrant Q&A, Help & Troubleshooting] brzgw:
Way back I had my brother's vibrant. And I put Eugene's gingerbread froyo rom. It was awesome. No problems. So then month later vibrant official 2.2 update released. I had made a nand back up in the recovery before flashing eugene's rom. So I went to recovery. Restore and back up. So it restored. It loads then freezes up on the lock screen. Then I managed to get it in download mode by holding volume buttons then plugging the usb. Recovery is impossible. Phone can't be detected by adb. Then in download mode. I wanted to go back to stock vibrant by Odin. I downloaded all the parts. Then it odin would just stall. I tried different versions. Nothing works. So when I got out of download mode, it rebooted then there was a phone icon exclamation mark and a computer. What does that mean? Can I fix it? Or am I done?

Sent from Glacier with CM7
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
use heimdall command close-pc-screen, it will get you out of phone--!--pc screen. Read this thread you will find links to Heimdall
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
You could always try to get into download mode again, that usually worked for me. Just take out the battery and then reinsert it after that attempt to hold both volume buttons with the power button but plug it into the usb right when you click the buttons. Then wait until the phone to pc icon flashes twice and let go of the power button immediatly after the phone flashes the second time.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I took my phone to UPS today. Anybody else send theirs back? If so, what's the progress so far?
[Vibrant Q&A, Help & Troubleshooting] brzgw:
Once I made up a story that I lost my phone then i found it and it wouldn't load.

Well it was my first time rooting. So I bricked. Maybe not call it brick. I was stuck on vibrant screen. Lol I sent it and they sent it back fixed.

Sent from G2 with CM7
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
Yeah, but your internal storage wasn't cooked either. Slightly different situation.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Did you get the replacement from TMO? If you flashed UVJFD on it before sending it back, you will be fine.
[Vibrant Q&A, Help & Troubleshooting] :
Mine has been sent back, received the replacement in three business days! Even received the text message that it was arriving after I received it. It came as stock KA6. I was almost, almost compelled not to root it. It ran super smooth even with rfs and over 5 pages of apps, web scrolling was smooth too. It came down to that stupid t-mo boot animation, and the terrible tw theming.
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
What was the turnaround time?
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Xdarooted did you send it to Tmobile or to samsung.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Rooting is fine, Voodoo for ext4 only is fine too, but personally prefer not to take risk with any OC kernel and kernels with voodoo sound and colors. I had tried all the custom ROMs and finally settled with stock UVKB1 with KB1+voodoo kernel.
[Vibrant Q&A, Help & Troubleshooting] :
I'm with you... no more oc kernels!
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Im with you guys too, I hope to god they repair my phone and after that, no more oc kernel
[Vibrant Q&A, Help & Troubleshooting] :
I sent it to T-mobile
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Will samsung repair it and if they can't then what will they do?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Don't worry. Samsung will repair it. First they will try to load the stock OS, which we know would not work. if that fails, they will replace the motherboard. TMO turn around is faster because they would send a replacement phone. TMO does not repair phone itself. Samsung repair may take some time.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I know, the samsung woman said it could take a week to 10 days to repair it.
[Vibrant Q&A, Help & Troubleshooting] raulcota:
Did you go through their support site or just take it to a t-mobile store?
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I would think he called them but I'm just guessing
[Vibrant Q&A, Help & Troubleshooting] :
I talked to support.
[Vibrant Q&A, Help & Troubleshooting] Halieus:
Still Trying to fix this thing

2 things to report:

1. I had removed and formated my external SDcard and believed it was working fine, but later discovered that my 4gb SDcard was only showing up as 2gd. My theory is that the problem is an partially fried SDcard not a data corruption thus partially working card post formatting. ("He's only MOSTLY dead") Therefore I believe the internal SDcard was fried. This could also explain why some were able to odin back and get a boot up and some weren't if some had a mostly fried internal SD and some had a completely fried SD. Just a theory let me know what you think.

2. I have a Ebay bid in for a screen shattered Vibrant and will attempt to replace the pcb which has the internal SD if I can win the bid with a reasonable amount of money. If anyone is interested in how this works out let me know. I will post my results on this thread.

I know I'm not the best educated mind in the room when it comes to this stuff so please let me know your thoughts.

Thanks!
[Vibrant Q&A, Help & Troubleshooting] Halieus:
42

I feel good about this appearing on page 42 of the thread. 42 being "the answer to life the universe and everything."
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
It is fried internal sd card. It is not data corruption or external sd card. Data corruption can be fixed by flashing JFD. Are you using Eugene's JK2 Froyo? if so, till JK5 the kernel had a bug, the external sd cards were showing as 2 GB when mounted on PC. You maybe seeing 2 GB because of JK2. It has nothing to do with DOW kernel crash and damaging your internal sd card. Your external sd card should be fine. You will see full 8 GB if you use your external sd card on a vibrant with latest froyo release.
[Vibrant Q&A, Help & Troubleshooting] Halieus:
2gb 4gb

The card only shows up as 2gd no matter what I use to view the card. I connected it directly to my laptop via the built in sdcard reader and it still can only see 2gd so something is wrong with the sdcard that was not before the DoW crash. I don't claim to understand exactly what's going on, but I can verify that something happened to the sdcard which was in use as my external sdcard.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Have you checked in device manager, after putting into your PC card reader. Maybe reformatting on PC would fix it?
[Vibrant Q&A, Help & Troubleshooting] Henchman:
You can't partially fry an sdcard .

I had the same problem .

Reformatted it in my vibrant 4g, and regained the missing memory .

You have accidentally created a non fat 32 partition .

You need to find a way to delete that partition .
[Vibrant Q&A, Help & Troubleshooting] Henchman:
Btw. I completely killed mine by flashing a UK Rom .

Nothing brings it up. Not even my download jig.

I'm getting a replacement sent.

I'm hoping that if I can't get it to boot at all, not even by using my jig, they can't either . And won't realise I screwed the phone up myself.

What do you guys think ?
[Vibrant Q&A, Help & Troubleshooting] Halieus:
2gb 4gb

I did a complete reformat from the pc and it only sees 2gb. Also, I was using it in my g1 and it seemed like the sdcard was corrupting the ROMs somehow. I'm not really that worried about the sdcard though I was just thinking about what this evidence might tell us about what happened to the phone.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I have just received my vibrant back from samsung and now it is working perfectly, I just flashed back to stock and sent it in. I wanted to ask you guys, since some of you can download apps and the phone died because of voodoo. Since you can't access recovery, why no just download the app voodoo sound from the market. This app gives you access to voodoo lagfix. I wish you all the best of luck and thank you for all your help. If any of you finally get it fixed, then stay away from overclocking kernels for good.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Voodoo is not OC. If you flash a kernel without OC, but only Voodoo lag fix, you should be safe. Market voodoo application does not flash voodoo, it is just a user app to control voodoo sound. you can flash kh6+voodoo. I was using kb1+voodoo since long time without problem. Since couple of weeks I am using overstock 1.3 kernel (it has no OC) and it runs smooth.
[Vibrant Q&A, Help & Troubleshooting] warfenix:
Thay makes me worry i flashed the same ketnel.... Gonna flash something now just to be safe
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
flash same kernel? Do you mean flashed DOW gain after it had bricked so many phones?
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Can anyone tell me the easiest way to root the samsung vibrant on ka6 firmware and also flash clockworkmod on it. This firmware has recovery 3e on it.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Use SuperOnceClickroot 1.7 http://xdaforums.com/showthread.php?t=803682

Install ROM Manager from market. After installing ROM Manager from market, launch it and use Flash ClockWorkdMod Recovery to install clockworkmod.

After you root the phone, you either search XDA for modified 3e recovery which does not search signature and flash it using ROM Manager, or in ClockWorkMod recovery under advanced there is an option to disable signature checking. I prefer modified 3e recovery which does not check signature of zip files.

After rooting, if you want to get rid of pink TMO boot animation, and shutdown TMO loud music, let me know, I will post mine boot screen with no music and shutdown animation with with very low volume jazz music.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Alright thank you but I don't mind the tmobile boot screen but do I have to flash the modified 3e recovery, if so how exactly do I do it. I mean doesn't the 3e recovery not allow me to flash clockworkmod
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Here is the link to install modified 3e recovery, Install it, then install clockworkmod

http://xdaforums.com/showthread.php?t=833423
[Vibrant Q&A, Help & Troubleshooting] Binary100100:
I just got mine back too. Anyone have kernel recommendations? I'm thinking OverStock but I would like feedback prior to flashing because I can't bare being without my Vibrant again! :eek:
[Vibrant Q&A, Help & Troubleshooting] bluerison:
im having a problem with my vibrant i bricked it trying to update with samsung kies i can get into download mode but when i flash it back to stock it loads up but the computer does not recognize it it looks normal i can text although it lost all of my contacts but let me get to the point...whenever i turn off my phone it will not come back on i have to go to odin and reflash it back to stock each time can anyone help me?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
I am using OverStock since two weeks. It is stable and fast. You will be fine with overstock, but avoid any other kernels with any kind of OC code in it. Overstock has no OC code in it.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
I have read several posts with similar problems. Kies is a messenger of death. I do not know why the hell Samsung cannot get their software bug free.

Anyway, Kies had damaged your bootloader. You need to flash UVJFD which contains a bootloader and a secondary bootloader (sbl), or, you can ODIN Eugene Froyo JK2. It had been discussed in this thread. Eugene Froyo JK2 has bootloader and sbl, it should fix it. Then flash again UVJFD. It should fix your problem.

After UVJFD, root your phone, and flash a clockwork flashable KA6 instead of updating via Kies-junk.
[Vibrant Q&A, Help & Troubleshooting] Henchman:
I would flash the Sweet Honey ROM.

That's what I flashed after receiving my replacement vibrant.

It flies.

Best ROM I've used by far.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Is it not Overstock 1.4 in that ROM makes it snappy? I am using KB1 with overstock 1.4 kernel and gets same performance as Sweet Honey ROM?

The OverStock kernel is fast and it makes any 2.2 ROM snappy.

EDIT: On stock KA6 which came with your fixed/replacement vibrant if you flash only OverStock 1.4 kernel, I am sure you will get same or almost same performance as Sweet Honey, rest is themes difference?
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I tried to install a modified recovery 3e but when I click on it, it goes through with success until it tries to get temporary root in which I already have root. So once it fails at that part, I choose option 2 on the list which I believe states to reboot and install but at that point the adb server does not recognize my phone. When I first start the process, the adb server goes with success. Any suggestions on what I should do.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
That is typical error of su recognizing adb as unkown.

Go to App Drawer and start su

leave it on

and now start 3e recovery installer

watch your phone screen, you will notice su complaining an unknown is trying to access root

on your phone press allow button

rest of the operation will proceed smooth

you will need to do this only once, after that su will always recognize adb

or as an alternative

you can start adb shell

and type

su - unknown and hit enter

then get out of adb shell by typing exit twice

now use 3e recovery installer and it should work

I hope this helps
[Vibrant Q&A, Help & Troubleshooting] bluerison:
can u please link me to those files i dont know how to get them
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Can you be more clear? Which files and what do you need?