yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I still can't install the modified recovery 3e, it keeps on failing
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Are you sure, you are rooted?

if yes, Go to market and search for "Superuser Update Fixer"

Install "Superuser Update Fixer"

Run "Superuser Update Fixer" to fix Superuser issues

Go back to market and search for Superuser

update your Superuser.apk

Now try 3e_recovery_installer.zip from http://xdaforums.com/showthread.php?t=833423. You should install 3e recovery by double clicking on "install.bat"
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Someone was asking about OverStock kernel performance. I upgraded to OverStock 1.5 and after 3 days went back to OverStock 1.4.1. The 1.5 after 3 days made my phone too lagy. I suspect under voltage, which it had, a culprit. 1.4.1 was flawless and fast.
[Vibrant Q&A, Help & Troubleshooting] MLIGN:
So I was rooted and running Lidroid's ROM then I went to stock ROM (unrooted) then applied the 2.2 Update via Samsung Kies. It downloaded installed and then my phone never came back on. Tried to boot into download (nothing) nothing pops up on my screen at all I have tried all various ways to turn my phone on and it can't get anything to come up! Time to get a replacement or does anyone have any light on my problem?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
You need to get it into Download using vol+/- keys. I am sure you may not have USB Debugging turned on at this stage, otherwise, you could download adb and use "adb reboot download" from your PC.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I just did what you said and now it is still showing the vibrant screen for about 5-10 seconds and it is like in a boot loop kind of stage, but I think I should let it sit for 10 min. and see what happens
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I know how to get into download mode other wise how am I flashing all these odin files
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Were you in Download mode (A Yellow Droid with a triangle and shovel)? When you connect phone to ODIN, did you see a COM field turned yellow? Did you ODIN UVJFD.tar, and repartition using pit512? When you hit Start in ODIN what was the output in the window? Can you copy and post it? I do not believe you had your phone flashed with UVJFD. I suspect your UVJFD flash failed.

It is boot loop, then 10 min wait will not help.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
I took three pics, how do i upload them, if I cant upload them here, then do you have yahoo messenger, I think that is easier to chat
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Sorry, I did not mean you do not know how to get into download mode

but did you see a field turned green or blue and said COMPLETE when you odin UVJFD?

You should be able to attach picture here. I need to check, if this PC has a yAHOO messenger, id is same as this one.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Yes it does, it says either com 6 or com 8 sometimes, and the thing on the top says Pass and a number
[Vibrant Q&A, Help & Troubleshooting] vnamee:
JK2 is probably better to flash w/ a repartition if your phone is really screwed. It'll completely rewrite and repartition the phone, and eugene's JK2 will overwrite pretty much every partition save for the EFS I think. May be one of the other partitions is screwed.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
removed....
[Vibrant Q&A, Help & Troubleshooting] drewdude007:
Well I have tried everything possible and nothing!!!!! If you are running DOW kernel and get a kernel freeze then Odin back to stock JFD.... PHONE IS BRICKED!!! The only thing that would allow the phone to boot up was JK2 and then you get the mount error so without the phone memory all you can do is use voice, data, and wifi and thats it!
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
I read through posts at other threads. Even one TeamWhiskey member could not fix it and had to replace phone.

If with JK2 your phone boots and at least you can use data, phone and network etc, but cannot mount, perhaps /efs is corrupted. Have you tried this as a last resort to fix mount problem http://forum.samdroid.net/f60/tutorial-remounting-restoring-backup-efs-partition-3600/
[Vibrant Q&A, Help & Troubleshooting] drewdude007:
Yes it could be the efs but that link is for the Galaxy 3 not the Galaxy S. I did not back up my efs.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
I know it is Galaxy3. It was for reference. How about some of your friend with a Vibrant? make a backup of efs from his phone and give it a try?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Or, I can post the efs from my vibrant, if it helps. I have to leave for another, therefore I can do it after an hour.
[Vibrant Q&A, Help & Troubleshooting] drewdude007:
yes please and also i have my new vibrant... how can i copy the rfs from my new phone to my old one. This is getting above my pay grade. lol. I am willing to learn though.

*Edit: I am sure I will have to read that link again as it is 6am and i have had no sleep.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
OK, will post my efs.tar in a while.

This was the command on my phone

adb shell

su

dd if=/dev/block/stl3 of=/sdcard/efs.rfs

cd /sdcard

tar -cv efs.rfs >efs.tar

exit

exit

c:\ adb pull /sdcard/efs.tar

You many not be able to use /sdcard/ since you are having mount problems.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Attached is ODIN ready efs.tar from my Vibrant.

I hope this help.

Good luck

EDIT: WARNING. the efs.tar could over write your nv_data.bin file which may change IMEI of your phone. You may have to look at XDA how to fix it if that happen.
[Vibrant Q&A, Help & Troubleshooting] :
Where in odin do I put this?

Also, found a thread about dbdata.rfs.tar. Where would I mount this it I want to give this method a try?

Wondering if you could upload a dbdata.tar from your vibrant too.
[Vibrant Q&A, Help & Troubleshooting] a4 moda:
This is so aweaome.

I posted up the PSA 3 days ago to warn people of the potential of meltdown with certain rom/kernel combinations. I can't believed it was locked.

I'm stuck in the same situation drew. I can't believe nobody can figure this out. I have solicited help from devs and peers here on xda, but it's like we've got leporasy, nobody touches you.

in any case, I'll post up my combinations when I get to a comp.

Thanks for those of you who have tried to help.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Try putting under PDA. Honestly, I had never flashed efs.tar with ODIN. It is my best guess.

Heimdall had a particular command for flashing efs.rfs and dbdata.rfs. If you decide to use Heimdall instead of ODIN, then extract the tar files to get efs.rfs file. Heimdall does not flash a tar file. Here is a Heimdall tutorial link http://board.teamwhiskey.com/viewtopic.php?f=29&t=1196

In these type of extra ordinary scenarios, I prefer Heimdall over ODIN, as Heimdall let you flash individual components.

Another thought came to my mind, but it was never tested by myself. ODIN UVJFD with PIT512, with re-partition, reboot and reset F. time, AND PHONE EFS CLEAR checked. ODIN away, it will definitely erase your corrupted efs. Your phone may hang on Vibrant screen after reboot. I assume you have to ODIN UVJFD again with Phone efs Clear unchecked so. Just a thought. It is untested so try it at your risk please.
[Vibrant Q&A, Help & Troubleshooting] drewdude007:
So I tried flashing the rfs and still not working. I also tried to clear the rfs as you suggested and still won't boot up.
[Vibrant Q&A, Help & Troubleshooting] :
Same results me too. Tried a dbdata.rfs.tar I found... didn't work either. you will have to do the no battery hook up to odin after this in order to get it in to download mode.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Why do you think dbdata.rfs may fix the problem? dbdata.rfs are usually huge, depending upon what is installed on your phone. You will get all of my phone data transferred to yours, which may be junk for you. My 5 year old son plays with my phone 24 hours,. He has hundreds of games on it. Anyway, I will upload it somewhere and post a link in a while, if you think it can rescue you.

Below are various mount points, dbdata is mounted at /dev/block/stl10 on vibrant

adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"

adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096"

adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096"

adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096"

adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096"

adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"

adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096"

adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096"

adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096"

adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096"
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Drew

I guess, we have tried all the logical things which could be corrupted. I am afraid the phone is fried. Yours still boot after JK2 but no SD card mount?

Does adb recognize it? perhaps run the mount command, if you can:

adb shell

su

mount

and post the output. I am curious to know what is missing in the mount table?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Drew,

Can you confirm that it was /dev/blocked/mmcblk0p1 not /dev/blocked/mmcblk0p2?

on Vibrant /dev/blocked/mmcblk0p2 mounts to /data

The /dev/blocked/mmcblk0p1 and /dev/block/mmcblk0 are the mount points from International Vibrant I900.

If you are seeing the error /dev/blocked/mmcblk0p1, that means left over of DOW kernel are left somehow which are difficult to remove. These may be causing /data mount problems therefore phone boots into only recovery. DOW is based upon I900 source, not TMO Vibrant SGHT959.

Confirm the error please. If we can somehow clean it, then UVJFD should restore it and boot the phone.
[Vibrant Q&A, Help & Troubleshooting] drewdude007:
Yes I will check this when I get home from work tonight.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
OK, I guess I found a reference on how to fix it. It is for another Galaxy, but should be applicable to Vibrant. http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20

Replace stock PB31IMG.zip with stock UVJFD.tar abd where ever in command it is ext2, change it to rfs instead of ext2. Use their sdparted application to reformat the partitions properly, there is a link to download it.

I assume this should take care of /data and /cache mount issue. It is /data and /cache mount issue due to bad flash. Since partitions are screwed up, ODINing UVJFD or Eugene Froyo does not flash properly, leaving behind corrupted /data and /cache partition.
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
When I flash Eugenes Jk2 I get this in recovery

E:Cant mount /dev/lock/mmcblk0p1 (or /dev/block/mmcblk0)

(no such file or directory)

E:copy_dbdata_media:Cant mount SDCARD:

copy default media content failed
[Vibrant Q&A, Help & Troubleshooting] :
Progress...tested...still no internal mount... sending back to t-mo as JFD... hoping warranty holds... any thought?:

1a. After ODIN and Eugene_2E_JK2_Froyo.tar.md5 can't mount mmcblk0p1 or mmcblk0 but phone is able to start no internal sdcard

1b. Using adb and SuperOneClickv1.5.5-ShortFuse I'm able to push the parted files to /sbin.

1c. parted says that my mmcblk0p1 is loop formated - don't know if this is because it's eugene's rom or the dow14 kernel

1d. hoping this isn't evidence to voids warranty

1e. I'm thinking the parted method only works for corrupted i-sdcards. I think mine is worse than corrupted

1f. having trouble unmounting mmcblk0p1 so I can mount rm 1.

2a. After ODIN and Stock JFD only boot loops, don't really know what can't mount, suspect it's more of the same

2b. Able to adb but not root shell to push parted files.

2c. Unverified what prints out as my formats

3a. After ODIN and T959UVKA6_REV05_home_low_CL860813.tar.md5 only boot loops in to recovery... Can't mount dev/block/stl10

3b. Able to adb but not root shell to push parted files.

3c. Unverified what prints out as my formats

4a. tried the following with no success at all

4b. I9000B_JH4_JI3_JH2_JH4_VJ_ARO.tar

4c. EUGENE373_SamsungS_Froyo_PDA.tar

4d. I9000XXJPC_I9000OXAJPC With new .PIT and ODIN.rar

4e. tried the efs and dbdata tars, nothing.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
xdarooted,

so after UVJFD and Eugene JK2 you were able to push su and parted.

I have no idea what parted mmcblk0 loop is. I believe DOW corrupted /data and /cache partition on internal SD card and perhaps left it as corrupted ext4 partition. Parted methode is the last resort, if it cannot rescue you, I am afraid phone is fried. Did you run the following command

parted /dev/block/mmcblk0p1 mkfs rfs then at 1, type rfs and at option 2 type /data?

If it gives loop, its worth trying formating it as ext2 with parted, i.e.

parted /dev/block/mmcblk0p1 mkfs ext2, for option 1 type ext2 then type /data for 2.

Repeat same for cache partition /dev/block/stl11

if all goes well odin uvjfd with repartition, so ext2 gets clean up to rfs.

Well, I did try to help as much as I could and dig into this problem. NO offece to anyone -I flashed DOW a week ago, but my sixth instinct told me, my phone will be screwed up, so after 5 minutes I removed it by flashing KB1+voodoo. I guess, I was lucky.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
xdarooted

Is it possible to post the mount table? From adb run following

adb shell

su

mount >mount.txt

exit

exit

adb pull mount.txt

post the mount.txt file as attachment. Mount table may give more information on what exactly got screwed after DOW crash.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Ameedi,

Thanks. Perhaps, the DOW kernel crash had left /data and/or /cache partition as corrupted ext4 partition. Therefore mount fails.

sdparted, as I discussed in this thread, could be last resort to manually fix those corrupted partition.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
SDPARTED

My apology, sdparted takes only ext2, ext3 and ext4, therefore xdaroot may have gotten loop formatted error. Even one of those ext could be able to reformat SD card to the point where UVJFD with repartition could recover the phone. You may have to push cynogenmod_recovery 1.4 together with sdparted. Here are links with script to automat and instructions.

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

http://www.simplehelp.net/2009/09/28/how-to-partition-your-androids-sd-card-to-install-apps-on-it/
[Vibrant Q&A, Help & Troubleshooting] :
Thanks for the confirmations guys. Yes my mmcblkop1 is partitioned as type loop.... but when I try to mkfs ext2, I get an issue with that the drive needs to be unmounted first. This is where I get stuck.

On the note that my phone is french fired, do you think t-mo will know that I messed with my phone...
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
DOW Kernel crash may have made it French Fried with fried bacon ;-)

did you try to run sdparted with sdparted.txt script, according to this reference http://www.simplehelp.net/2009/09/28/how-to-partition-your-androids-sd-card-to-install-apps-on-it/, instead of doing manually? The sdparted.txt script should do ext4, but it should be OK. A successful ODIN of UVJFD/pit512 with repartition should be able to clean up, provided sdparted.txt script fix the corrupted left over ext4 partition.

EDIT: pull the SIM and external SD card before running sdparted.txt script.
[Vibrant Q&A, Help & Troubleshooting] :
I'll give this automation a try... I'll have to change some of the parameters in the sdparted.txt file it looks like... oh one last thing in adb shell if I try to ffdisk -a the mmcblk0p1 partition if gives me a ioctl <bml get dev info>... in guessing this is also because of the loop format.

Another note. I can't believe that I'm going to be the only one that will try this out, really...
[Vibrant Q&A, Help & Troubleshooting] Henchman:
I can't push anything. I get a no permissions error.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Did you first do SuperOneClickv1.5.5-ShortFuse before pushing anything?
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
The error means some bml is locked, see http://xdaforums.com/showthread.php?t=788299 That is a corrupted partition due to kernel crash, that is why re-flashing problems.

which lines do you think, you need to edit in the script? I noticed only /system/sd which should be OK if you pull the external sd card out.

I believe others are trying too...
[Vibrant Q&A, Help & Troubleshooting] anteko:
I'm having the same problems getting stuck in recovery <3e>... not sure what else I can try to fix this issue.
[Vibrant Q&A, Help & Troubleshooting] ssiddiqi1:
Of course after DOW kernel crash you get stuck at recovery. Are you trying sdparted to fix corrupted partition as discussed here?
[Vibrant Q&A, Help & Troubleshooting] ameedi600:
Did a fix come out for this, if it has then can someone make a video tutorial on how to fix it
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
I've been watching a couple of threads on this and no-one has reported success as of this writing.
[Vibrant Q&A, Help & Troubleshooting] :
Haven't had time yet... will post something tonight if the sdpated.txt works.
[Vibrant Q&A, Help & Troubleshooting] drewdude007:
I have tried EVERYTHING!!! Nothing has worked thus far. I have to send my old phone back to T-Mobile within the next few days so I won't be able try much more.
[Vibrant Q&A, Help & Troubleshooting] anteko:
Just tried the sdparted.txt method and am getting "error: device not found" after entering the "adb shell chmod 755 /sbin/sdparted" command.
[Vibrant Q&A, Help & Troubleshooting] :
exit adb shell and type adb device or devices to see that you are connected to your device.
[Vibrant Q&A, Help & Troubleshooting] wbexpress:
Dear felow commiserators: I am at least fortunate enough (for the moment) that everything is still functional. However, I am fairly certain that DoW14 src may have created some ugly for me as well. I installed & learned Heimdall the other night to flash the kernel, and yesterday the fun started. The symptoms are:

-I cannot mount the SD card. Does absolutely nothing, shows neither drive in "my computer" and of course does not automatically open & "autoplay" as it did before the fateful kernel flash -Although I am able to get into download mode, it does not recognize a COM port at all in ODIN, neither does it recognize one when the phone is normally booted, as it usually does

-I cannot get Heimdall to work, the "start" button is greyed out after putting the pit & tar files where they go

-I cannot get into ADB, it does not recognize the device

This was all discovered when I was trying to flash a new ROM last night, the obvious plan was to ODIN back to stock, and I was surprised to see ODIN not working. That's when I discovered the other issues. Do these symptoms sound like a likley by-product of the Dow kernel crashes? Is anyone else in the same boat? Any ideas for fixes? I suppose I could do the proverbial hard reset in "privacy", but I don't want to try to fix what isn't yet broken, since if it doesn't work I would, at best, be stuck with stock Eclair. TIA...

Edit: I just ried restoring a nandroid backup and I'm in an endless bootloop.
[Vibrant Q&A, Help & Troubleshooting] Droid-o-matic:
This is a little different than my scenario. I can successfully ODIN all day long. Trouble is it won't fix anything. Aren't the nandroid backups stored on the phone? If so that is also different as all I have for storage is where the OS is. The internal SD doesn't appear to exist any longer. Lastly, the hard reset you refer to will have no impact if you are indeed suffering the same fate.

Are you able to get the phone operating again and tell us what the amount of phone storage is indicated under settings?
[Vibrant Q&A, Help & Troubleshooting] anteko:
"adb devices" gives me "list of devices attaches", that's all.

Edit:

I got the sdparted method to work but I had to odin to Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-odin-pda instead of EUGENE373_SamsungS_Froyo_PDA... This is great progress :D
[Vibrant Q&A, Help & Troubleshooting] wbexpress:
Let me know if everything I say is completely responsive, as although I have done much flashing and some serious bricking, this is the first time I've had anything like this:

-Yes, I had 3 nandroid backups, but each one threw me into a bootloop.

-I actually never lost the functionality of the phone, it actually runs perfectly. I was trying to Odin when it happened, and I was going to flash Einherjar's 2.2.1. Since I can't see either card/drive, I took the external out and put it in a reader, put the ROM on it, put the card back in, used Root Explorer to transfer it to the internal card, flashed and it took perfectly. That's what's nuts about it.

-The phone storage available space available says 6.95? Is that the # you are looking for or 1.39 on the SD card?

-Yeah, I don't want to wipe everything and maybe then render what is currently working useless. Man, I hope someone can figure this out. It seems as though everything works for a few days, then something decides to go bonkers with no other input? I'll bet there are gonna be more of us in the same boat in not too long...
[Vibrant Q&A, Help & Troubleshooting] anteko:
I can confirm that the sdparted method DOES in fact work. I just finished flashing back to stock. :D
[Vibrant Q&A, Help & Troubleshooting] jangst123:
Too many BRICKS! Need to narrow this down!

I think we need to focuses on who bricked (how many) and the history of the phone + what was installed at the time!? Plus how many days before it Bricked!?

I'm thinking this Fried something in common with each of these phones.

Or

We all had something installed that others did not, or length of time running!

(It could be the others flashed something else before 3 days, while these Bricks managed not to flash anything for a few days)

We have 6 vibrants in our office, all running [ROM] Bionix-v 1.2.1 - Team Whiskey - 02/09/11 Running PERFECT in GPS and all around Philadelphia PA.

On 2 I installed DoW

On 12th I installed DoW on a New phone in this manor: Rooted with SuperOneClick, installed Titanium, Rom Manager, then flashed Bionix-v 1.2.1, waited 15 min, rebooted, waited 10 min rebooted, then flashed DoW, waited 15 min and rebooted, waited 10 rebooted, then installed, SetCPU, Bloater (installed Audio postcard, Kindle, Memo, Slacker) and I believe that is it! I try to keep my installed fairly clean for the 1st 4 days.

SetCPU Profile at time of Brick: Screen Off, Max 800, Min 200, Scaling conservative,,,, Other Profile Battery<25 Max 1400, Min 200, Scaling conservative

On the 2nd maybe 3rd day I awoke to what I thought was a dead battery,, see below links for more info.

I had installed DoW on a 2nd phone on the 13th, but seeing that I and a few others had bricks around the 3rd day I quickly removed it from this phone by flashing Stock KA7 Kernel

See http://xdaforums.com/showthread.php?t=952537 for more information and http://xdaforums.com/search.php?do=finduser&u=3341031

If all the Bricks can list what your phone was running at the time, what you were running before, what you installed, how you installed, how long you were running DoW, over-clock settings, maybe we can narrow it down!

Or maybe we were all unlucky and fried some component of the phone by over-clocking
[Vibrant Q&A, Help & Troubleshooting] jangst123:
Who or what is sdparted!? More information please!
[Vibrant Q&A, Help & Troubleshooting] Henchman:
Can you tell us exactly how you got it to work. And five links to the files you used.

It would be greatly appreciatef.