So yesterday everything was going great, thanks to Frost being released, i downloaded it, went to CWM, i clicked install, and it was in the progress of flashing, but then i get this:
E: Cant symlink /system/bin/cat
E: Failure at line 16:
symlink toolbox SYSTEM:bin/cat
Installation aborted
Then i Odin to stock, and re-downloaded, same thing happened, I Odin'd to stock again and checked Re-Partition this time and still no luck, then i was like forget it. So i flashed Trigger26.zip...and i get THE SAME RESULTS! so i then Odin'd the third time and i was like ill just flash Bionix 1.3...i do it and the SAME thing happened, EXPCEPT it looked different, it said this:
E: Cant symlink /system/bin/su
E: Failure at line 16:
symlink /system/xbin/su SYSTEM:bin/su
Installation aborted
So instead of it saying bin/cat like in the Frost error
is said bin/su in the Bionix error...
I dont know what to do i cannot flash anything at all, i know i shouldnt be posting this here or whatever the haters wanna say, i jist need help..
Thanks for reading my desperate post and for trying...i hope help reaches soon!!
I don't know where you got your Odin and the files for stock but try downloading re-installing Odin and the files from here:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
These work great and I have heard of people having bad/damaged files before.
If not, try the CWM config:
http://forum.xda-developers.com/showthread.php?t=833423
or:
http://forum.xda-developers.com/showthread.php?t=734164
Good luck!
I had a similar issue once and was able to get it fixed by flashing (in Odin) Eugene's Froyo That Doesn't Brick, then going back to stock and starting fresh.
I looked for a download link but couldn't find one. Check out Google and if you can't find a download link, let me know and I'll upload it.
follow the above posts they are correct but here is the sequence for a reminder:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the JFD file for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
Good luck.......................... sheesh
oka1 said:
follow the above posts they are correct but here is the sequence for a reminder:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the JFD file for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
Good luck.......................... sheesh
Click to expand...
Click to collapse
I tried this, except my phone didnt error out and i was on JK2 froyo, so then i just went back to download mode, checked re partition, put the pit and the JFD and when i did it, my phone was stuck on the vibrant screen! what do i do now? am i eternally bricked?
You are not bricked, just stuck in boot loop. Shouldn't have checked re-partiton, try running the process again, only with two checkboxes checked, no re-partition.
Sent from my SGH-T959 using XDA Premium App
OR run the same process again just remeber to put PIT file in to PIT place and click repartition ,if u wont put pit file dont check repartiton, but u have to check repartitoin now since u have done this without pit file and u checked repartition do it again with pit and repartiotn .
put pit in to pit field
put JFD.zip in to PDA field
check repartition
Thanks guys ill try it, and even though i am getting the "E:" error, i can still flash Axura but not bionix, frost, or trigger....
thats really weird ........
Are you wiping each time this happened to me a while back and a quick fix was to just wipe everything (data,cache,dalvick cache, battery stats, etc.) Just wipe.
Sent from my Vibrant using XDA App
bartek25 said:
OR run the same process again just remeber to put PIT file in to PIT place and click repartition ,if u wont put pit file dont check repartiton, but u have to check repartitoin now since u have done this without pit file and u checked repartition do it again with pit and repartiotn .
put pit in to pit field
put JFD.zip in to PDA field
check repartition
Click to expand...
Click to collapse
Worked me out of boot loop, but still getting the error
Sent from my SGH-T959 using XDA App
duboi97 said:
Are you wiping each time this happened to me a while back and a quick fix was to just wipe everything (data,cache,dalvick cache, battery stats, etc.) Just wipe.
Sent from my Vibrant using XDA App
Click to expand...
Click to collapse
Ill try that, but when you wiped, ddid you do it on stock Rom?
Sent from my SGH-T959 using XDA App
Nabeel10 said:
Ill try that, but when you wiped, ddid you do it on stock Rom?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No bionix v to bionix v 1.2 no wipe (I still had to wipe....)
Sent from my Vibrant using XDA App
thank you
weissbach said:
thank you
Click to expand...
Click to collapse
To who?
Sent from my Vibrant using XDA App
Related
ok here we go i installed bionix earlier with the voodoo fix than went to flash Frankin_final..... after that my phone wouldnt start up regularly so i panicked and went into recovery and did a system format and a data format..... now i dont know what to do period cause when my phone start up it got into recovery help!!! I HAVE PAYPAL I AM WILLING TO SEND $5 (for a beer) to first person who can help me either via PM or regularly please!!!
frankiedizzle87 said:
ok here we go i installed bionix earlier with the voodoo fix than went to flash Frankin_final..... after that my phone wouldnt start up regularly so i panicked and went into recovery and did a system format and a data format..... now i dont know what to do period cause when my phone start up it got into recovery help!!! I HAVE PAYPAL I AM WILLING TO SEND $5 (for a beer) to first person who can help me either via PM or regularly please!!!
Click to expand...
Click to collapse
u didnt mention, did u undo voodoo? u have to before installing another rom or making a backup,
try getting the JI6 .tar file and flash via odin 1.3
sheek360 said:
u didnt mention, did u undo voodoo? u have to before installing another rom or making a backup,
try getting the JI6 .tar file and flash via odin 1.3
Click to expand...
Click to collapse
i didnt but does it matter cause i erased my whole system sd internal and external
frankiedizzle87 said:
i didnt but does it matter cause i erased my whole system sd internal and external
Click to expand...
Click to collapse
it does matter here try this
Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
Fix 1:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
Fix 2: (use only if you know how to use adb commands)
1. Place the 'disable-lagfix' file in your sdk>tools directory
2. Get into clockwork recovery like you normally would
3. Follow these adb commands to push the 'disable-lagfix' file to you sdcard>voodoo
adb push disable-lagfix /sdcard/voodoo
4. File should now be on your sdcard in your voodoo folder.
5. Reboot phone and with luck, you should hear Linda the robot telling you your file system is being converted back to rfs.
6. Because your system directory has already been wiped, you'll still get a black screen when you reboot, but your file system is back to rfs. Just pull the battery, and reflash whatever rom you want. Then reboot again.
this is from sombionix from his bionix 1.6 thread
frankiedizzle87 said:
i didnt but does it matter cause i erased my whole system sd internal and external
Click to expand...
Click to collapse
Sending you a pm
Find the vibrant bible thread and flash through odin call me 816 505 9131 ask for will
Sent from my SGH-T959 using XDA App
will_n said:
Find the vibrant bible thread and flash through odin call me 816 505 9131 ask for will
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
lol good laugh call u w/ no phone
I am un bricked
Sent from my SGH-T959 using XDA App
frankiedizzle87 said:
I am un bricked
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Then Will might want to take his phone number down, lol
Hello all, I'll give my story chronologically.
1. Installed Clockwork Recovery.
2. Did a nandroid backup. Everything OKAY at this point.
3. Tell Clockwork to partition my SD card.
---- It does its thing, reboots phone into recovery to partition SD, then upon reboot, it will get past initial T-Mobile Spash and Galaxy S splash but will not proceed further (black screen when phone would normally load up).
Figuring I'm ****ed, I try p much everything. Even going back into recovery for some reason brought me back into stock recovery instead of clockwork.
Damn.
4. Installed Odin, flash back to stock, no problems or errors detected during odin-ing process.
5. Phone goes through start-up, same issue.
Whaaa? Please help, as this really sucks. The phone is obviously not bricked, but it might as well be because it's about as useful as... well, it's not very useful in the current state.
Thanks for any help that can you offered.
edit: All my datas are gone. D:
Also, I can get into download mode (obviously) and recovery mode. Here is what I see in recovery mode.
" -- Movi_check Start..!!
checksum confirmation need_checksum[1301305579]
MBR_ChkSum in header : 4.1
MBR checksum : EC0063A432AFDBA2B104C3F0DF52FE3D
MRB Checksum Error
Movinand Checksum Confirmation Fail
-- movi_checking done!...
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC "
Click to expand...
Click to collapse
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
metalfan78 said:
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yep, that's what you have to do and then make sure NOT to partition your sd card again. Bad things happen with that. As you have seen
Yea, never partition with clockwork. Just out of curiosity why did you partition in the first place
Sent from my SGH-T959 using XDA App
metalfan78 said:
Yea, never partition with clockwork. Just out of curiosity why did you partition in the first place
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The clockwork app said there was some advantage or another. I can't quite recall anymore.
Anyways, working on following all of the advice now, guys. Thanks a bunch.
ok so here is what you have to do:
1. download odin, froyo that doesn't brick, and 2.1 true stock
2. go to download mode, flash the pit and tar file from the froyo that doesn't brick (DON'T RE-PARTITION!)
3. it will boot into recovery and error out, DONT PANIC, that is what is supposed to happen
4. remove battery (from phone) and usb from phone and computer
5. put battery back in, access odin and download mode
6. flash the pit and tar file from the true 2.1 stock (RE-PARTITION THIS TIME!)
7. if done successfully, your phone software will like when you just took it out of the box!
Thanks. Typing this from eugenes froyo now. I almost do not want t go back to 2.1 now. Haha
edit: does eugene have any fully-functioning 2.1 builds? i really love the stockyness of his froyo. reminds me of when i was playing with the i9000 in korea over the summer and doesn't have all of the disgusting gradients that the tmo builds have.
edit: I think I can deal with the switched volume, non-functioning 3.5mm jack, and no home button. This version of android is what i've always wanted. TMOBILE TAKE NOTE. Haha. Can't wait for this to be bug-free.
Edit again... ok i miss the home button
I have the same exact issue.
Only problem is that the steps explained here do not fix the problem.
Shouldnt this procedure wipe out your internal SD?
Mine is never wiped out. I get to Froyo/ no brick with no issues.
No errors in recovery once I "adb reboot"
Flash back to stock with repartition and back to the same checksum error.
Cant figure out why this wont erase and rebuild the NAND.
Anyone???? Maybe an ADB commant to manually repartition and erase the entire internal SD?????
sknobs said:
I have the same exact issue.
Only problem is that the steps explained here do not fix the problem.
Shouldnt this procedure wipe out your internal SD?
Mine is never wiped out. I get to Froyo/ no brick with no issues.
No errors in recovery once I "adb reboot"
Flash back to stock with repartition and back to the same checksum error.
Cant figure out why this wont erase and rebuild the NAND.
Anyone???? Maybe an ADB commant to manually repartition and erase the entire internal SD?????
Click to expand...
Click to collapse
Did you download the correct "Eugenes Froyo That Does Not Brick"? Its titled exactly that.
Click here for the thread
cthach11 said:
Did you download the correct "Eugenes Froyo That Does Not Brick"? Its titled exactly that.
Click here for the thread
Click to expand...
Click to collapse
Yep, thats the one.
It even saved some of my email settings. I was shocked!!!
I did the adb reboot
It booted and after boot.......ding, you have a new email. Had all my account settings and all.
I have done the odin flash over and over, never erased the nand once?????
metalfan78 said:
You need to odin 'eugenes froyo that doesnt brick' first, search for that thread, then odin stock
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you so much for this info...I thought I was going to have a nice paper weight after only 8 days of owning my Vibrant!
Do exactly what this says.
First EUGENE373_SamsungS_Froyo_PDA.tar and s1_odin_20100512.pit
then when phone reboots, use
s1_odin_20100512.pit and Original.tar and and all is good
hi
Did you repair your phone？
where to download the 2.1 true stock
I searched but didnot find
thanks
The Tech Game said:
ok so here is what you have to do:
1. download odin, froyo that doesn't brick, and 2.1 true stock
2. go to download mode, flash the pit and tar file from the froyo that doesn't brick (DON'T RE-PARTITION!)
3. it will boot into recovery and error out, DONT PANIC, that is what is supposed to happen
4. remove battery (from phone) and usb from phone and computer
5. put battery back in, access odin and download mode
6. flash the pit and tar file from the true 2.1 stock (RE-PARTITION THIS TIME!)
7. if done successfully, your phone software will like when you just took it out of the box!
Click to expand...
Click to collapse
said323 said:
where to download the 2.1 true stock
I searched but didnot find
thanks
Click to expand...
Click to collapse
Having the same issue, ended up ODIN with eugene and had a somewhat working phone, just couldnt download anything. Once in Euegne froyo, should I load anything onto SD card (mounting it to computer) or adb push anything somewhere???
After reverting to a stock image Im back where I started
Have tried the following 2.1 tars: JI6 & JFD
I'm able to get back to stock but not sure if its the correct stock rom. I still get the mbr checksum error when rebooting into recovery. If I did the correct rom would the mbr checksum error be done with?
I can't seem to get this to work either.
Tried Eugene a thousand times.
Stock ROM- MBR error in recovery
Only 4 lights at bottom...
Have read about 20 hours of same problem on multiple forums with no avail.
Was it Voodoo Lagfix? How do I remove it or FIX MY INTERNAL PARTITION SIZES?
First of all this is probably all my fault for not unrooting my Vibrant before trying to flash the stock rom through Odin. I've tried different versions of Odin and the flash is successful, but I'm getting a black screen after the "S" during start up. Sometimes the keys will light up, other times they won't. I'm using the right .tar and .pit files as well. I'm still able to boot into recovery and download mode. I'm at a loss right now and considering just trying to get a new Vibrant from T-Mobile somehow.
AimlessWanderer said:
First of all this is probably all my fault for not unrooting my Vibrant before trying to flash the stock rom through Odin. I've tried different versions of Odin and the flash is successful, but I'm getting a black screen after the "S" during start up. Sometimes the keys will light up, other times they won't. I'm using the right .tar and .pit files as well. I'm still able to boot into recovery and download mode. I'm at a loss right now and considering just trying to get a new Vibrant from T-Mobile somehow.
Click to expand...
Click to collapse
I'll share with you the steps I go through when reverting to bone stock JFD.
Go HERE and get Odin3 v1.70. Earlier versions, especially v1.00 are as buggy as a roach motel.
Go HERE and get the JFD Odin3 package, including the 512.pit file and the JFD pda file.
Load them (as you seem to know how to do) and be sure to click REPARTITION before proceeding with the flash.
I'd also suggest removing the external SD and sim.. I've never personally had to do this, but you might as well...
Let me know if this succeeds or fails...
You should check out'eugenes froyo that doesn't brick' search for that. Using that method through odin and then stock will wipe everything, including your internal sd card, but it should get you up and running again. It's a pain but it should do the trick
Sent from my SGH-T959 using XDA App
metalfan78 said:
You should check out'eugenes froyo that doesn't brick' search for that. Using that method through odin and then stock will wipe everything, including your internal sd card, but it should get you up and running again. It's a pain but it should do the trick
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Good man! I was gonna suggest that as the next step!
If my initial clarifications failed (I was being specific primarily about the need to repartition) to help..Then do the procedure HERE, which is flashing Eugene's brick liberating Froyo first before using Odin3 to revert back to JFD..
note: this requires you having a working and functional install of the AndroidSDK found HERE.
Thanks and thanks for posting links, I can't do that yet
Sent from my SGH-T959 using XDA App
AimlessWanderer said:
First of all this is probably all my fault for not unrooting my Vibrant before trying to flash the stock rom through Odin. I've tried different versions of Odin and the flash is successful, but I'm getting a black screen after the "S" during start up. Sometimes the keys will light up, other times they won't. I'm using the right .tar and .pit files as well. I'm still able to boot into recovery and download mode. I'm at a loss right now and considering just trying to get a new Vibrant from T-Mobile somehow.
Click to expand...
Click to collapse
since you already have the original jdf.tar im assuming. all you need to complete the equation is the froyo that doesnt brick as a few others have already said. you will lose everything on sd card.
step 1: load up ODIN
step 2: select the pit file that you have already
step 2: select eugenes froyo.tar as the pda selection
step 3. turn off phone and take battery completely out
step 4: plug usb cable into phone and computer (battery must still be out)
step 5: push and hold both vol +/- keys and insert battery.
Step 6: if done correctly, you should know be in download mode (yellow triangle, actually says downloading lol) if not repeat steps 3-5 until successful then continue to step 7 (one of the com windows should light up displaying com:4 for example but could be any number..
Step 7: select repartition, auto reboot, and f. reset time. NOTHING ELSE.
step 8: click start.
Step 9: assuming that it doesnt hang anywhere, the blue progress bar should slowly continue to move until finish and phone boots into recovery (probably gonna through an error. doesnt matter)
Step 10: battery pull
Step 11: repeat steps 4 and 5 now
Step 12: this time select same pit file
step 13: for the pda file select ...uvjdf.tar (the one you originally tried to flash that landed you in this situation).
step 14: uncheck repartition this time. (only f. reset time and auto reboot should be selected)
step 15: click start.
Step 16: if it hangs, repeat steps 10-15.
step 17:it will reboot into recovery. then select reboot phone now.
step 18: assuming that all was done correctly, you should have your phone back exactly how it was the day you bought it, minus the sims3(sacrifices)
I feel like your phone may have been burned by dragons recently. lemme know if it works.
Gave your idea a try masterotaku and the outcome was the same. I'm now trying the "eugene's froyo that doesn't brick". I'm unfamiliar with Android SDK. Do I just install it and thats it?
Flashing to eugene's froyo that doesn't brick and then flashing back to stock worked. Ya'll saved my phone! Thanks for all ya'll help. This has got to be the most quick to respond forum and most helpful one I've been apart of. Thanks again. Is there like a points system here or something I can use to show my gratitude?
high im new to the vibrant flashing. ive been here for awhile started with g1 then to nexus one now vibrant. ok i rooted n flashed rom and phone was running great. i was running axura 2.2.7.1 and i came acrossed this vodoo kernel http://forum.xda-developers.com/showthread.php?t=870480. And i flashed it from the sgs flash kernal app and when it rebooted it said some bout no rom on partion and wouldnt boot. so i went to recovery to nandroid and my intire internal sd was wiped clean. so i data reset and tried flashing a rom and get this....
Formatting system...
formatting cache....
formatting datadata...
formating data....
E:can't mount /dev/block/mmcblk0p2
(file exists)
error mounting /data/!
skiping format...
deleting files....
deleting files...
deleting files...
E:can't mount /dev/block/mmcblk0p2
(file exists)
copying files...
copying files...
E:can't mount /dev/block/mmcblk0p2
(file exists)
E:can't mount data:
E: failure at line 13:
copy_dir PACKAGE:data DATA:
installation abort
and when i boot the phone it gets stuck on the vibrant boot and i think it says convert system partion.
ive never fully bricked a phone before is this what a full brick is??? can some one please help me who knows this stuff better and if you can fix it i will donate very generiously if someone will take the time to help thank you for your time.
Sounds like a case of odin and restarting. Pretty easy think the odin stuff is a sticky in the general portion of vibrant section. It's almost impossible to f up this phone beyond fixing.
Sent from my SGH-T959 using XDA App
Gibsonusa said:
Sounds like a case of odin and restarting. Pretty easy think the odin stuff is a sticky in the general portion of vibrant section. It's almost impossible to f up this phone beyond fixing.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
ok yeah when i came from the nexus one i saw the odin and vodoo stuff but stupid me didnt research it any figured everything was like nexus... wow was i wrong things little different on here ill look into the odin thing and if i can get it back to runinng i will donate to you if able. if i cant would you be willing to help me further. im not a noob just its lot different from the nexus one.
how do i get odin from herehttp://forum.xda-developers.com/showthread.php?t=848737 i download the one that says odin but its just a rar file and dont do any thing. how do i put the files with it?
did you even try to extract the one that you download?
iynfynity said:
did you even try to extract the one that you download?
Click to expand...
Click to collapse
for some reason on the rar file its not letting me have an extcart option sorry if all this is a lil dumb not the biggest comp. person. screen shot attached
kamikazimonky said:
for some reason on the rar file its not letting me have an extcart option sorry if all this is a lil dumb not the biggest comp. person. screen shot attached
Click to expand...
Click to collapse
you need winrar in order to open rar files. not sure if 7zip can do it, but it's worth a try (seeing as it's free and all).
Oniyuri said:
you need winrar in order to open rar files. not sure if 7zip can do it, but it's worth a try (seeing as it's free and all).
Click to expand...
Click to collapse
7zip worked fine and i put them in and click start and does nothing n i am in download screen on vibrant.
kamikazimonky said:
7zip worked fine and i put them in and click start and does nothing n i am in download screen on vibrant.
Click to expand...
Click to collapse
not sure what is up but this might help
http://www.youtube.com/watch?v=KyAIUOYufrU
Part 2: http://www.youtube.com/watch?v=33I-aNCypVM
Your gonna need ODIN and eugenes froyo that doesnt brick
You will also need 512.pit and JFD.tar file .. you can get these via the Bible sticky ..eugenes froyo is on his site..
Try to see if you can get into Download Mode:
Pull everything out ..battery, sim, scdard
Open ODIN and leave it on your PC
Plug the USB cable into the PC
Put the battery back in
Hold down on both of the volume buttons
Plug the usb into your phone...keep holding the buttons
It should go into D/L mode....we hope..
If it gets that far..make sure you see a yellow COM port in ODIN
Not sure with eugenes froyo but 512.pit goes in the PIT line
eugenes froyo.tar goes in the PDA line
I think you may need Repartition checked in your case to get the filesystem back but if his site says not to then dont.
Hit start
This is not a daily driver ROM...just to allow you to re ODIN
If it works...again we hope... You need to go back into D/L mode
check for COM port
add the 512.pit & this time the JFD.tar to PDA
uncheck repartition and hit start
and hopefully you will get back to stock 2.1
one question did you repartiton your internal sd with rom manager or just voodoo it ?
jmcghee1973 said:
Your gonna need ODIN and eugenes froyo that doesnt brick
You will also need 512.pit and JFD.tar file .. you can get these via the Bible sticky ..eugenes froyo is on his site..
Try to see if you can get into Download Mode:
Pull everything out ..battery, sim, scdard
Open ODIN and leave it on your PC
Plug the USB cable into the PC
Put the battery back in
Hold down on both of the volume buttons
Plug the usb into your phone...keep holding the buttons
It should go into D/L mode....we hope..
If it gets that far..make sure you see a yellow COM port in ODIN
Not sure with eugenes froyo but 512.pit goes in the PIT line
eugenes froyo.tar goes in the PDA line
I think you may need Repartition checked in your case to get the filesystem back but if his site says not to then dont.
Hit start
This is not a daily driver ROM...just to allow you to re ODIN
If it works...again we hope... You need to go back into D/L mode
check for COM port
add the 512.pit & this time the JFD.tar to PDA
uncheck repartition and hit start
and hopefully you will get back to stock 2.1
Click to expand...
Click to collapse
im having trouble finding the eugenes froyo.tar file anywhere.
edit: i believe i found it at the right place will try it out http://eb-productions.net/vibrant/vibrant-unofficial-tmo-2-2.html
bartek25 said:
one question did you repartiton your internal sd with rom manager or just voodoo it ?
Click to expand...
Click to collapse
just vodooed it never mest with partitions with the card
Also not sure what version of odin you might be using. I used odin v1 and it wouldn't work for me after more looking around read that v1.7 was the one that would work. I think that one is in the q&a stickies says like root odin stuff like that. Also found that the pit that ended in 12 worked better than the one that ended in 13. Fact I also couldn't get 13 to work either.
Sent from my SGH-T959 using XDA App
Gibsonusa said:
Also not sure what version of odin you might be using. I used odin v1 and it wouldn't work for me after more looking around read that v1.7 was the one that would work. I think that one is in the q&a stickies says like root odin stuff like that. Also found that the pit that ended in 12 worked better than the one that ended in 13. Fact I also couldn't get 13 to work either.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
well both 1.0 or 1.7 neither reconize my phone now for some reason and windows says im missing dirver s or some that hardware wasnt installed right. man this is getting so frustating and i love this phone
Ill get on computer in a minute and tey to peovide you some links
Sent from my SGH-T959 using XDA App
Samsung drivers for your computer so it picks up the phone.(just read the things to click i had a ***** of a time finding it and thought that you had to buy the software but you dont im just not that great at looking at what i need to be clicking on.)
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
A nice little how to unfunk your vibrant and how to get it into dl mode
http://forum.xda-developers.com/showthread.php?t=848737
Odin 1.7 rar files
http://forum.xda-developers.com/showpost.php?p=8863820&postcount=138
(sorry if you have this stuff but these are the steps that i went threw when i had boned my phone pretty hard)
Eugene 2.2 stock odin thingy
dont use the odin that comes with this btw i know i didnt or i think i tried and it was dumb and wouldnt work.
http://www.mediafire.com/?cb8vpwob8hz6yxv
alright man so go step by step unpack the sammy drivers and open odin 1.7 then plug in your phone SHOULD find your phone after you get those drivers installed on your comp. any port will do when odin finds your phone.
put the 512 pit file in the pit spot (uncheck repartition if it is checked)
then put the tar file or what not in the tar spot and click start it SHOULD only take about 3-5 minutes depending think it took me less then two but everyone seems to have different times i guess.
When you are back to stock let it sit a minute or 5 reboot to work out whatever kinks it might have then find you a rom and flash. FOLLOW THE DEV INSTRUCTION ON WHATEVER ROM YOU PICK. hehe pm me if you still have problems, shouldnt though
Hi I have a samsung vibrant that was running bionix v and it suddenly bricked itself. So i decided to use odin as I have in the past but this time when I get into download mode, it says key pressed, 164 on the top. I then use odin and it flashes successfully but once it reboots it stays on the vibrant screen for about 5-10 seconds and then it shuts itself off. I think its because im using an ld version of odin, which is odin 3 v1.7. I really need help please
Where you using a stock kernel?
Sent from my MB200 using Tapatalk
I am having this same exact exact problem.
I am soo pissed. I have been running fine with Bionix, then day 2 after installing DOW kernel, my internal memory card is fried.
I mean absolutely FRIED.
I can't get past boost screen *(It shuts off like yours does too)
I can't ODIN with anything, because it shuts off. If I try to plug it in, it will just battery charge loop.
I'm at a loss here too.
I've installed Eugene's OC kernel, TTbal's OC kernel, and the old DOW OC kernel's fine. Everything has been great. My phone handled 1.4 like a champ.
But now, nothing works. NOTHING.
*sigh
I also installed dow kernal and then a few days after that it just suddenly decided to shut itself off
Sent from my T-Mobile myTouch 3G Slide using XDA App
If it turns on its NOT bricked....this term is soooo loosely used.
odin back,reflash and allow 10-15 minutes to set up after full boot
Sent from my SGH-T959 powered by TW's Bionix V1.2.1,DOW.
ameedi600 said:
Hi I have a samsung vibrant that was running bionix v and it suddenly bricked itself. So i decided to use odin as I have in the past but this time when I get into download mode, it says key pressed, 164 on the top. I then use odin and it flashes successfully but once it reboots it stays on the vibrant screen for about 5-10 seconds and then it shuts itself off. I think its because im using an ld version of odin, which is odin 3 v1.7. I really need help please
Click to expand...
Click to collapse
If it turns on then it is not bricked, although it can be frustrating to fix it.
I will suggest following
1) Start ODIN and get Vibrant in download mode
2) ODIN Eugene's Froyo-that-does-NOT-brick. Do not check re-partition in ODIN. Do not use PIT512 file to re-partition
3) Reboot
4) Start ODIN again and get your Vibrant in Download mode again
5) ODIN PIT512 file and UVJFD stock, make sure you check repartition in ODIN this time.
6) Reboot
7) Re-root and install ROM Manager from Market
8) CWR flash or ODIN whichever version of ROM you like.
I hope this help.
You're probably in luck because the phone still turns on. In the future try to be real specific about what you were doing leading up to the bricking, things usually don't suddenly brick themselves. Follow ssiddiqi1's instructions and you should be fine.
Sent from my Vibrant using XDA App, Bionix-v 1.21
Try this: http://forum.xda-developers.com/showthread.php?t=954509
There have been several people, including myself, who have had this problem. No matter what you Odin, Including Eugene's no brick fix, the phone will not boot into recovery mode after Odin flashes a .tar file. No combo of .pit and .tar files work and it dose not matter what version of Odin you use. Nothing works. Trust me people the phone is BRICKED and there is no fix for it. Sorry.
Some threads about the same problem.
http://forum.xda-developers.com/showthread.php?t=955593
http://forum.xda-developers.com/showthread.php?t=956164
http://forum.xda-developers.com/showthread.php?t=955623
http://forum.xda-developers.com/showthread.php?t=957675
drewdude007 said:
There have been several people, including myself, who have had this problem. No matter what you Odin, Including Eugene's no brick fix, the phone will not boot into recovery mode after Odin flashes a .tar file. No combo of .pit and .tar files work and it dose not matter what version of Odin you use. Nothing works. Trust me people the phone is BRICKED and there is no fix for it. Sorry.
Click to expand...
Click to collapse
Version of ODIN does not matter, I agree. But if phone turns on, it is not bricked. Probably partition is messed up. Eugene no brick froyo (without a PIT file and no repartition) should get the phone to boot into a buggy vibrant 1900 version, then ODIN with PIT512 and repartition should get you back into bootable phone with fixed partition.
As I said it is frustrating but it is fixable. I had exact same scenario with Eugene Dead Horse kernel. The steps I wrote in my other posting, fixed the problem.
EDIT: You do not need Recovery mode. Recovery is not going to do any good due to messed up partition. You need only Download mode for ODIN to ODIN no-brick-froyo then UVJFD.
ssiddiqi1 said:
Version of ODIN does not matter, I agree. But if phone turns on, it is not bricked. Probably partition is messed up. Eugene no brick froyo (without a PIT file and no repartition) should get the phone to boot into a buggy vibrant 1900 version, then ODIN with PIT512 and repartition should get you back into bootable phone with fixed partition.
As I said it is frustrating but it is fixable. I had exact same scenario with Eugene Dead Horse kernel. The steps I wrote in my other posting, fixed the problem.
Click to expand...
Click to collapse
So I just tried it again to be sure. I flashed Eugene's no brick Froyo with no .pit and re-partition NOT checket. I then flashed JFD with the 512.pit and checked re-partition. I get the same results... Odin flashes and says completed at which point it should boot into recovery and finnish doing its thing. However all the phones with this problem fail to boot into recovery and just keep showing the battery charging, turn off, and show the battery charging picture over and over until I unplug the usb. At which point I press the power button and it boots up to the Vibrant splash screen the shuts off. This happens every time.
Sent from my MB200 using Tapatalk
Drewdude
Why should it boot into recovery after you ODIN JFD and repartition. It should reboot normal. Are you sure, you have a good UVJFD.tar file? A while ago, UVJFD odining messed up my phone. It was bad UVJFD.tar file. I would recommend go to Teamwhisky web site at http://www.teamwhiskey.com and look for Shorty's File Locker. I used UVJFD, PIT and ODIN from Shorty last week and it worked. Here is a direct link to it http://board.teamwhiskey.com/viewtopic.php?f=3&t=1322
Also successful Odining of Eugene's no-brick-froyo should boot you into a normal boot with a few errors, no Recovery. If needed, I can upload my copy of Euegen's no-brick-froyo, which had always helped me.
The ONLY .tar file that would flash and boot up the phone is the JK2 .tar found in this thread.
http://forum.xda-developers.com/showthread.php?t=799105
However, after flashing it I get the this error message and the phone does not access to the internal or external memory card.
E:Can't mount /dev/blocked/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
After Odin the phone will not boot up at all. I have downloaded the .pit and .tar files from Team Whiskey's site and i get the same thing.
drewdude007 said:
The ONLY .tar file that would flash and boot up the phone is the JK2 .tar found in this thread.
http://forum.xda-developers.com/showthread.php?t=799105
However, after flashing it I get the this error message and the phone does not access to the internal or external memory card.
E:Can't mount /dev/blocked/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
Click to expand...
Click to collapse
I think, you are not getting your Internal SD card partitioned properly, therefore mounting issue. Maybe download again pit512 file from Shorty's File locker? Sometime during download files get corrupted. Its worth downloading it again. Also in ODIN check options Re-Partition, Auto Reboot and F. Reset Time. Do not check Flash Lock, Do not check Phone EFS Clear and Phone Bootloader.
I had been using ODIN3 v1.81. Karylon360 posted it on XDA a few days ago. YOu should find it in Vibrant Dev Section.
EDIT: See dan0zone post below
drewdude007 said:
The ONLY .tar file that would flash and boot up the phone is the JK2 .tar found in this thread.
http://forum.xda-developers.com/showthread.php?t=799105
However, after flashing it I get the this error message and the phone does not access to the internal or external memory card.
E:Can't mount /dev/blocked/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
copy default media content failed.
Click to expand...
Click to collapse
There are files on the data side of JDF that is needed to boot if you wiped everything ... so if you got JK2 to boot to this error then ODIN to JDF and you should be good ....
No matter what when I Odin JFD, and I have downloaded and re-downloaded the .pit and .tar files from from Team Whiskey's site as well as others, I get the same results and the phone won't boot.
I am getting a replacement phone, thank god. However, I would really like to find a fix for this so I do appreciate all the help!
I did post this problem on Team Whiskey's Facebook page if anyone would like to see all the things I did yesterday. Just scroll down and look for my (Andrew Neubauer) post.
http://www.facebook.com/home.php?sk=group_180393771989565&ap=1
I still need help, I am now stuck on the setupconnection on odin, I was going to try to flash eugenes no brick but I cant find it on xda. Can someone please help me and can someone also maybe post a link to eugenes no brick
nevermind I got through the setup connection part Thank you to all that helped