Ok, here's the story...
I rooted my T-Moblie Vibrant with the Update.zip file via this link "forum.xda-developers.com/showthread.php?t=723479"
Everything worked fine and I tried to do the VooDoo lag fix and all **** happend via this link
"androidspin.com/2010/09/23/overclock-add-some-voodoo-to-your-samsung-vibrant/"
I also applied the "Dalvik-cache & Data Scripts" and "JAC’s OC Kernel + Voodoo Beta4 Kernel " to my phones SD card. At this time, I flashed "Clockwork Recovery" and enetered it to apply the two .zip files to my phone. I installed both .zip files containing the ""Dalvik-cache & Data Scripts" and "JAC’s OC Kernel + Voodoo Beta4 Kernel " AT THE SAME TIME and I then tried to reboot and apply. At this time "LINDA" the robotic voice operator notified me of all the steps and in the end congratulated me for the successful application of the .zip file.
Once the Vibrant screen came up, it NEVER continued, frozen for an hour, I looked at alternative options and tried ODIN... ODIN3+SPL, s1_odin_20100512.pit, SAMSUNG_USB_Driver_for_Mobile_Phones_x86 (32bit)[I AM AWARE MY COMPUTER IS 32 BIT], T959UVJFD.tar. These were all the files used to flash the Original Rom back to my Vibrant. I used several others and NOTHING WORKED, I MEAN NOTHING... THE FARTHEST I GOT IS THE GALAXY S SCREEN AND IT GOES (BLACK RIGHT AFTER ALONG WITH THE ABILITY FOR THE FOUR KEYS ON THE BOTTOM OF THE SCREEN TO BE LIT IF PRESSED) What's weird is that the charging battery screen pops up and it charges, I'm assuming that the software is properly flashed back. I just bought this phone and I'm so frustrated...
CAN ANYONE PLEASE HELP ME... I feel like chukn' this phone at the wall, but $500 will be gone(((((((( TIA...
if the 512 flash doesnt work, try flashing to i9000 rom eu, then flash to 512. i had to do that when i bricked my phone flashing a rom and not disablling voodoo
Yea I agree, try froyo that does not brick thru odin
Sent from my SGH-T959 using XDA App
Just had this issue with my phone last night, couldn't get it back even using odin and going back to JFD. I ended up at a T-mobile store today and they are replacing it for free except for shipping. Hopefully you have better luck but you should be able to get it replaced if you can't. I was expecting them to tell me no luck but they went ahead and replaced it. I did fail to mention that I may have caused the software issue though....
Email me [email protected]
Sent from my GT-I9000 using XDA App
Its baaack!!!!!
Just got my phone running! Follow the steps in this thread, you first download eugenes froyo to your phone through odin and then immediately flash stock 2.1 through odin and your phone is fixed. I am so happy right now!
Here is the thread with full instructions:
http://forum.xda-developers.com/showthread.php?t=745547
Hello,
I tried to recovery my phone by using Odin3 to install the stock 2.1 vibrant rom. I am using the rom from the official sticky about fixing a bricked phone.
Odin3 1.0 did not work and it would always freeze on a process even after trying it over and over again at least 5 times. So, I changed to use Odin3 1.7 which I found a link to on xda. This one installed successfully and went through the whole process and my phone rebooted. When it rebooted I saw the Samsung Vibrant Screen, then the T-Mobile screen then the Galaxy S screen fine like normal. But once it got passed the S screen a black screen would come up and all the button lights stay lit up and nothing happens for hours. I tried installing the rom several times, tried different links to the offical JFD stock rom, but everytime I try to install the same thing would happen. What do you recommend I should do to fix this problem?
wipe cache partitin , factory reset in rrecovery ?
Yes, I did. I wiped cache and data, but it still is is still stuck at the black screen.
Your using the JFD.tar in PDA and 512.pit in PIT and Repartition is NOT checked?
Yes, I made sure it was not checked and It was checked automatically the first time and I didn't realize that odin checks that automatically, so I unchecked it and did it a second time. The phone still gets stuck at the black screen with light up buttons.
I am trying the Eugene's Unofficial Froyo rom right now because what initially bricked my phone was installing 2.2 from Kies and that failing. When that failed I unplugged the phone and got the computer to phone icon screen and could no longer boot, so I went to install the stock rom.
The problem I am having with Eugene's Unofficial Froyo rom I am having now is that I have 0 space for applications and cannot install applicants even after doing a wipe and factory reset. Does this have to do with accidently setting it to re-partition and if so, how can I fix the no application storage issue so that I can install applications?
Thanks
I was thinking he designed this ROM just specifically to help bricked vibrants...I think you just use it as a means to reflash another ROM or back to stock or whatever.
I did what you had phone ! PC.. last night to my wife's phone....left it on that screen and plugged into pc with ODIN open..it showed a COM port so I flashed it like that and it boots right up.
I wonder if it has anything to do with Voodoo? I had a Voodoo Lagfix installed prior to doing the upgrade to Froyo 2.2 using the official method. May be why it failed. so I decided to flash back to stock. When I flashed stock 2.1 the phone would boot up then show the Vibrant Screen then the T-Mobile intro then the Galaxy S intro but once it got passed that the screen would go black and the buttons would stay lit up. I flashed Eugene's unofficial 2.2 ROM (no longer posted on xda, but it is on his website). That booted up perfectly, but the problem was that I now had 0 application storages and apps could not be installed on internal memory (could still install apps on SD card, I used this to install Rom Manager to the SD Card to flash Clockwork Recovery just in case)
Today, I tried flashing the Stock 2.1 rom back onto it (Phone was currently running Eugene's rom), but I have the same result with the black screen and lit buttons.
I looked at the FAQ for removing Voodoo and added a folder named "disable lagfix" in the Voodoo folder on the internal SD card. I ran this, but the problem still persisted, so I decided to flash again to see if it would be fixed. Still the same thing occured.
If this is a Voodoo problem, is there another method for removing Voodoo that I could try? I need to make sure that it is restored to the default RFS file structure that came with the phone and flash stock 2.1
Hmmm...odin back to eugenes froyo & unmount ur internal sd & format...go ahead and remove ur microsd & sim also...& then try to odin just the. Tar for jfd no pit ...no repartition..try to use ka6 instead of a 2.1..
Sent from Bionix V powered Vibrant
flash back to JFD eclair from bible with 512 pit and repartition ticked .
just for record JFD.zip goes in to pda
ViralCipher said:
I wonder if it has anything to do with Voodoo? I had a Voodoo Lagfix installed prior to doing the upgrade to Froyo 2.2 using the official method. May be why it failed. so I decided to flash back to stock. When I flashed stock 2.1 the phone would boot up then show the Vibrant Screen then the T-Mobile intro then the Galaxy S intro but once it got passed that the screen would go black and the buttons would stay lit up. I flashed Eugene's unofficial 2.2 ROM (no longer posted on xda, but it is on his website). That booted up perfectly, but the problem was that I now had 0 application storages and apps could not be installed on internal memory (could still install apps on SD card, I used this to install Rom Manager to the SD Card to flash Clockwork Recovery just in case)
Today, I tried flashing the Stock 2.1 rom back onto it (Phone was currently running Eugene's rom), but I have the same result with the black screen and lit buttons.
I looked at the FAQ for removing Voodoo and added a folder named "disable lagfix" in the Voodoo folder on the internal SD card. I ran this, but the problem still persisted, so I decided to flash again to see if it would be fixed. Still the same thing occured.
If this is a Voodoo problem, is there another method for removing Voodoo that I could try? I need to make sure that it is restored to the default RFS file structure that came with the phone and flash stock 2.1
Click to expand...
Click to collapse
When you do the disable lagfix are you rebooting and letting it convert the filesystem back to rfs or are you just powering down and going to d/l mode and trying to ODIN? You need to reboot the phone and let Linda do her thing and power up, then power down etc etc..
jmcghee1973 said:
When you do the disable lagfix are you rebooting and letting it convert the filesystem back to rfs or are you just powering down and going to d/l mode and trying to ODIN? You need to reboot the phone and let Linda do her thing and power up, then power down etc etc..
Click to expand...
Click to collapse
Yes, I rebooted after applying the disable lagfix, but it booted normally and didn't seem like it was doing the Linda thing....I wasn't sure if it worked or not. How would I know if it is back to using the RFS system?
I tried different roms and I had no luck. The KA6 Rom that flashes via odin installs fine, but it goes to the Recovery Screen the E3 one I think, and when it tries to mount DATA and other partitions it fails to do so, and somethings fail to be wiped. It doesn't boot.
When I run the JFD odin, when it goes to recovery for the first time it has one error where it fails to wipe DATA. Not sure if these are the reasons why I am having problems though.
I formated all partitions including the internal sdcard. Still no luck.
So far the only ROM that I got working is Eugene's 2.2..but I can't install applications with that one.
I tried installing the Bionix V Rom via ClockWork Recovery, but once it begins to Copy Files it errors out with an Error on line 13 and copy's out an error log. I posted a response to the thread about this ROM. I redownloaded to ensure it wasn't corrupted.
*****If you need more information on the EXACT Rom I installed prior to the brick here is the thread to the rom I installed. Maybe that will help you help me more ******
This is the rom I had before attempting to upgrade to Froyo:
http://forum.xda-developers.com/showthread.php?t=791478
I installed the Stock Recovery version.
Edit: I know this rom above is a kernal mod. I did flash the stock Vibrant kernel prior to installing the JFD ROM from this link: http://www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar
crap dude do yo uhit repartition when u flash ka6 ? if so dont do so if its only update , dont check partiton if you flash just an update , hit partitoon if u flash offical release .
yes go back to jfd repartiton update to ka6 withou repartiton
bartek25 said:
crap dude do yo uhit repartition when u flash ka6 ? if so dont do so if its only update , dont check partiton if you flash just an update , hit partitoon if u flash offical release .
yes go back to jfd repartiton update to ka6 withou repartiton
Click to expand...
Click to collapse
When I install the JFD with or without repartition I get passed all the boot screens, but it screen goes black and buttons light up..Sorry if I am being a noob and missing something obvious...but I followed those instructions, and I did it multiple times as well.
FIXED!!!
I fixed it wohooo!!!! I flashed Eugene's Froyo that doesn't brick version then flash back to stock JFD and its working perfectly! Thanks XDA! Found out that a lot of people with this issue after having Voodoo installed and installing a different rom, and that this rom was made to fix the Voodoo brick. Funny thing is the Eugene's rom fails on recovery with errors in this case, but it still unbricks the phone lol
Ahhh see lagfix didnt disable..glad you got it working..
Thanks for your help. I now am using the Bionix-V Rom with the Dragon-Kernel Voodoo and let me tell you I love this phone even more now with this Rom. Loving the Gingerbread theme and it runs super fast. Stock is too slow for me lol Anyway, this is resolved no more offtopic posts lol...
ViralCipher said:
I fixed it wohooo!!!! I flashed Eugene's Froyo that doesn't brick version then flash back to stock JFD and its working perfectly! Thanks XDA! Found out that a lot of people with this issue after having Voodoo installed and installing a different rom, and that this rom was made to fix the Voodoo brick. Funny thing is the Eugene's rom fails on recovery with errors in this case, but it still unbricks the phone lol
Click to expand...
Click to collapse
would you please tell all the steps you did to make it work
I have a Vibrant and have used many other roms but have flashed any thing like 6 months so I wanted to try something new and saw that CM7 was working now. I flashed back to stock, than flashed to whatever the link is right after install talking about froyo bootloaders at this link http://forum.cyanogenmod.com/topic/17020-all-models-cyanogenmod-7-for-samsung-galaxy-s-phones-build-20110303/ than tryed to install it "the hard way" but now it just keeps rebooting try to reflash ClockworkMOD recover or something. any ideas?
I did the same thing. You need to be on a froyo rom to install CM7.
I odin'd back to stock, installed Bionix -v 1.2.1 then disabled voodoo. I then cold booted into CWM and installed CM7. Worked good that way.
how did you do that. it just keeps going in a circle booting.
You will need to go into download mode.
Phone off (battery pull), hold vol up and down together, while holding - plug in USB.
Odin should then recognize it.
Re Odin back to stock, root, upgrade to a froyo rom then upgrde to CM7.
okay I just got back to stock again, at least it looks like it! But I am still getting an odd thing. when the phone is booting the first screen that comes up is not vibrant its gt-I900 any ideas?
yay ur getting the 1900 bootloader because u have both on ur phones!
how do I fix this? I just flashed back to Bio 1.2.1 and its still there
well now I did it... think I just really bricked it this time. I did what the post by a400meter said to do at this link http://forum.xda-developers.com/archive/index.php/t-756832.html and now it wont even turn on!
I have rooted and installed roms on my vibrant a lot of times...Im not sure I I got into this problem..
-When rebooting to recovery from rom manger, it says signature verification toggle failed
-I toggle signature toggle and everything works fine, until I reboot and try again
I have ODIN'ed back to stock and even re-rooted..still same problem
-When the phone boots it has 2 screens, galaxy s i9000 and then vibrant?
-I have tried changing kernel and everything else I can think of...
Somebody please help me!
-right now Im running bionix 1.3.1, I have also tried to run this from the simply honey roms as well
Well don't understand what the real issue is, but if the custom rom has a ported Galaxy kernel then you would see the Vibrant then> I9000 splash screen or vice-versa
That is not a problem it is supposed to do that
Odin back to stock JFD Make sure to back up everything on the computer then> make sure to click repartition box then flash the re-root then load Rom manager and then flash ---->
Trigger, Bi-winning or Malice from EDT.......... I guarantee what you see will be something much more to your liking.....
Good luck..........
So I am on Malice brutal rom and want to try the new gingerbread bali kernel. I have the gingerbread boot loader if it make a difference. so i flashed the Kernel cleaning script as suggested in OP then flashed bali kernel and rebooted. I then got stuck in a boot loop. It will show the vibrant screen, then the bali screen, then show a recovery screen but it flashes by too fast to read what it says, then goes back to the bali screen for a few seconds before rebooting. I cannot get into recovery but I can get into download mode. any suggestion on how to fix this? I'm thinking of flashing CM7 through odin or going back to JFD first but am worried about the fact that I had the gingerbread bootloader and voodoo lagfix enable and whether either will cause complications.
Solved it on my own. I flashed revolution with heimdall and it seems to be working fine now. I relieved that it was an easy fix, I was worried for a while.