I sold my friend my Samsung Vibrant and I've never had any problems flashing it, he tried flashing the cyanogenmod rom (tried being the operative word...) and I'm not sure what he did to but when I try to turn it on its has the I9000 boot screen and it goes to the vibrant splash screen and turns off, if it's plugged it gets to the vibrant screen and then has the cycle icon for the battery then it shows the battery and it infinitely loops like this when its plugged in (when I had it, it would be completely dead and I could plug it in and turn it on at the same time and it would boot fine and didn't die). I tried flashing JI6 via ODIN, which seemed to flash correctly (gets to zImage and says removed and then pass), but nothings changed (still I9000 boot screen and still crashes on splash screen with battery loop). Any idea what I can do to fix this?
I think your friend flashed the I900 Version of the Rom. Try odin-ing to stock.
EDIT: You already odin-ed JI6. Try odining to stock JFD with both pit and tar files. That should restore everything (bootloader, kernel, baseband, etc...)
its shows i9000 on boot with the GB bootloaders
http://forum.xda-developers.com/showthread.php?t=849028 have a read through there
if you do have the GB bootloaders its vol up and power for download mode
odin to stock will fix it
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
ddaydude said:
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
Click to expand...
Click to collapse
go there:
http://forum.xda-developers.com/showthread.php?t=1230059
skip the parted part you dont need it and phone would be back to good function asap.
ddaydude said:
Downloaded and tried all three of these things and still nothing different. When I turn it on the boot and splash screen come up but then the device just turns off. Tried JI6 and JFD, and the boot screen keeps showing up as the I9000 (GB), when it should be the stock TMOUS bootscreen, so it seems like the bootloader isn't being flashed correctly, although it says pass and has no errors. I'm thinking that the phone is bricked, is there anything I'm not thinking of that would help?
Click to expand...
Click to collapse
the jfd.tar doesnt have the bootloaders i dont think so you'll still be on GB bootloaders on 2.1, they're backwards compatible anyway so it doesnt matter
demetris_I said:
go there:
http://forum.xda-developers.com/showthread.php?t=1230059
skip the parted part you dont need it and phone would be back to good function asap.
Click to expand...
Click to collapse
I've tried to get into recovery mode for this but I can only get into download mode (tried VOLUP+HOME+POWER (and without home) boots to download mode, tried VOLDOWN+HOME+POWER (and without home) and it does nothing, I've tried to use adb on the download screen but it doesn't find the device). Is there another method that I'm missing?
I remember telling you you dont need parted part -> dont need to enter cwm just download mode.
1.download mode
2.http://www.4shared.com/file/dJiyRz3v...Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
demetris_I said:
I remember telling you you dont need parted part -> dont need to enter cwm just download mode.
1.download mode
2.http://www.4shared.com/file/dJiyRz3v...Froyo_PDA.html
unzip it and get odin ready.
Go to download mode, place pda only in phone area pit not needed, flash
Let it boot into recovery, remove battery and re-enter download mode.
Flash JFD with pit file and re-partitions checked.
Done and done.
Click to expand...
Click to collapse
Sorry about that, my bad. But I tried just tried that, and when I flashed the Froyo file it booted to recovery (like it sounds like it should have, still with GB bootloader and reversed controls on recovery and not able select since vibrant doesn't have an ok button) and then flashed JFD with the pit and repartition selected and it goes back to turning off after the vibrant screen. I tried redownloading both froyo and JFD thinking one might be corrupt and I still get the same result as before. I've checked the instructions 10+ times and I've used odin for the life of this phone more times than I have counted, and I can't figure out why it doesn't seem to be taking it, it doesn't fail in odin so it doesn't make sense.
After doing what i recommended your phone would be in fully functioning order.
Your problem lies on the bootloader so i would recommend to flash froyo bootloader from here:
http://forum.xda-developers.com/showthread.php?t=1117990
but before md5 check the downloaded file and follow exactly the guide there.
If this dont fix it then i think your phone is a pita.
I kinda agree that its probably just the Bootloaders that is the culprit for the I9000 splash. As mentioned flashing the original FROYO should fix it. At least it did for me. I had to do both these links in the GB bootloader thread for it to take though. 1st one 1st - then either of the 2nd links 2nd.
adyscorpius said:
jfd odin file - for use after installing gingerbread bootloaders
http://www.multiupload.com/hryjkflkfq "thanks to laylovj"
md5: 977e2136996e7138945447a8245d6776
if you have gingerbread bootloaders installed and you end up odining to stock (jfd), you will notice it changes the bootsplash to i9000. You can either reflash a gb bootloader again, or simply use the odin package above to do so.
vibrant stock (froyo) bootloader download link
- dropbox download link
- mediafire download link
md5 sum - 754ecbd8e76d4f81bec49240031f3262
Click to expand...
Click to collapse
Now as far as ODIN. The yellow triangle and android dude digging should be there throughout the entire ODIN flash. If I understand you correctly and the phone goes black during the ODIN flashthats no good. If its doing it after the ODIN flash, then maybe you still have the "reboot after flash" button ticked. Either way the phone needs to stay in download mode during the entire ODIN flash.
*EDIT*
- If all else fails JTAG! but that should be the last option. There is a fix!
- BUY A USBJIG you can get them from either TeamWhiskey or EDT on their sites. If everyone had one we would never see another
"NO DOWNLOAD MODE!!! HELP" thread again. And at the same time you'd be supporting developers which is a good thing.
Good luck!
You should try the "froyo that does not brick" in the early days of froyo eugene released a froyo package that came with bootloaders. Google ftdnb, it may also be in either bricked or eb's threads
Beware of angry gingerbread man
Related
After trying to partition the EXT feature within CLMR once my phone reset it came back up with the boot screen everything normal than nothin but a blank screen. I go back Reflash with Odin and Current Vibrant-Tmo image on here. Result was delayed audio for TMobile start up GIF and sound and no Screen response. Wen tback attempt #2 with Odin/T959UVJD flash phone resets and goes absolutely dead. Remove battery same thing. Anyone else have trouble with Clockwork Mod's partitioning?
I also noticed if you get the phone-!-pc error just running the 512pit file seems to fix it atleast it did for me.
If you had read up on here, you would know that Clockwork tries to partition the internal flash and breaks your phone. You need to Odin flash with the "re-partition" box checked. That should fix it. I have posted a ZIP you can flash that will parition the external card properly, you can edit the script and change the partition sizes if you like, it's set to create a 1GB partition for EXT4 with the remainder as FAT32.
It has been said several times in several places...
DO NOT PARTITION WITH CLOCKWORKMOD RECOVERY
I reflashed with Odin and checked Repartition and thats when it just died after reset, no power no nothin.
I also made the noob mistake of partitioning with clockworkmod . However, my device wasn't bricked. instead, it left absolutely zero memory left for third-party apps and the like. I'm not sure if I should reflash with ODIN since my issue isn't as serious as a brick. Any experienced members on this thread please help.
honoluluacx said:
I also made the noob mistake of partitioning with clockworkmod . However, my device wasn't bricked. instead, it left absolutely zero memory left for third-party apps and the like. I'm not sure if I should reflash with ODIN since my issue isn't as serious as a brick. Any experienced members on this thread please help.
Click to expand...
Click to collapse
Follow this
http://forum.xda-developers.com/showthread.php?t=745547
^ Since the links in that thread no longer work (Eugene left XDA), all you need to do is flash eugenes froyo that doesnt brick (sounds like you have it), pull the battery when done, then flash the stock ODIN pit/tar for JFD, Fixed.
True, that works even better
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html
s15274n said:
^ Since the links in that thread no longer work (Eugene left XDA), all you need to do is flash eugenes froyo that doesnt brick (sounds like you have it), pull the battery when done, then flash the stock ODIN pit/tar for JFD, Fixed.
Click to expand...
Click to collapse
So do I need to reflash eugene's froyo rom or, since I already have it, skip the reflash and go straight to odin? Also, thanx in advance for all the helpful senior members.
HELP!!! I followed the instructions to the letter, but after about three attempts with ODIN, by vibrant still won't boot up. I can still get to download mode, but can't reboot.
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
honoluluacx said:
HELP!!! I followed the instructions to the letter, but after about three attempts with ODIN, by vibrant still won't boot up. I can still get to download mode, but can't reboot.
Click to expand...
Click to collapse
Are you online?
I followed the guide. Unfortunately, the device hanged during the reboot. I didn't do anything during that time, so I threw in the towel and told T-Mobile I tried to update to 2.2 and sent it in. Thanks for the links though.
This will seem long, but I want to ensure whoever may be able to help has all of the info I can give. My vibrant is officially bricked..
1)I was on the newest official software JI6
2)I had installed RyanZA's One click lag fix
3)I reversed the One click lag fix
4)Got creative and decided to try voodoo lag fix for vibrant version 3
5)After installing voodoo, phone will not boot
6)Here are the symptoms after voodoo.....phone will turn on and attempt to boot, but then just sits there with the bottom four buttons lit
7)Next, I have tried the following:
a)Odin JI6 - same result, phone will not move past Galaxy S logo
b)Did a factory reset - then Odin JI6 again = same result
c)Odin stock 2.1 (JFD) with 512 pit = Same result
Please help!
I had to odin my phone like 4 times to get it to work... Odin is the way... Have you tried switching the usb port the phone is plugged into?
Try using Odin and flash back to stock ROM prior to JI6 like JI2 or JFD. This should work
mightykc said:
Try using Odin and flash back to stock ROM prior to JI6 like JI2 or JFD. This should work
Click to expand...
Click to collapse
I have tried 2 times now to go back to JFD. Same result, everything goes smooth, then the Galaxy S logo appears. Once the Galaxy S logo goes away, the bottom four buttons stay lit for a while, and then I just have to power on. It stays in this loop.
clemsonboyz said:
This will seem long, but I want to ensure whoever may be able to help has all of the info I can give. My vibrant is officially bricked..
1)I was on the newest official software JI6
2)I had installed RyanZA's One click lag fix
3)I reversed the One click lag fix
4)Got creative and decided to try voodoo lag fix for vibrant version 3
5)After installing voodoo, phone will not boot
6)Here are the symptoms after voodoo.....phone will turn on and attempt to boot, but then just sits there with the bottom four buttons lit
7)Next, I have tried the following:
a)Odin JI6 - same result, phone will not move past Galaxy S logo
b)Did a factory reset - then Odin JI6 again = same result
c)Odin stock 2.1 (JFD) with 512 pit = Same result
Please help!
Click to expand...
Click to collapse
I believe the reason your phone would not boot is b/c you were running JI6 and flashed the voodoo kernel. To the best of my knowledge ALL of the custom kernels available for the Vibrant are based off of the JFD build. You have to flash the zip from this thread http://forum.xda-developers.com/showthread.php?t=804415 THEN flash the kernel you want to use. I also know that once you flash the .zip from that thread, if you try to revert to the STOCK kernel it will hang at the Vibrant screen. Only way to get back to stock STOCK is to use Odin. Now as to why Odin is not working is beyond me... I almost wonder if it converted your RFS to EXT4 even though it hung at the Vibrant screen. If this happened then to fix it I believe you have to use Odin to flash Eugene373's "Froyo that does not brick" then downgrade back to JFD and then upgrade back to JI6. It won't be fun, but hopefully this will help you get up and running again!
Update!
Tried again using odin to JFD.
I noticed that after the blue bar finished in download mode and the screen starts scrolling things...
there was an error. It said it was unable to reset data.
Afterwards, it reboots while odin is finishing, then it shuts the phone off...
I would love to try this, but I believe this is over my head. (No shame here!) I don't know how to flash using clockwork.
clemsonboyz said:
Tried again using odin to JFD.
I noticed that after the blue bar finished in download mode and the screen starts scrolling things...
there was an error. It said it was unable to reset data.
Afterwards, it reboots while odin is finishing, then it shuts the phone off...
Click to expand...
Click to collapse
I think its safe to say if you are having a data error then voodoo IS enabled on your phone. You either need to do what I said earlier and flash Eugene's Froyo that does not brick and then downgrade back to JFD OR you might be able to use adb to push a file named "disable lagfix" (no extensions) into the "Voodoo" folder on your sdcard to disable voodoo. You need to disable it before your phone will work.
clemsonboyz said:
This will seem long, but I want to ensure whoever may be able to help has all of the info I can give. My vibrant is officially bricked..
1)I was on the newest official software JI6
2)I had installed RyanZA's One click lag fix
3)I reversed the One click lag fix
4)Got creative and decided to try voodoo lag fix for vibrant version 3
5)After installing voodoo, phone will not boot
6)Here are the symptoms after voodoo.....phone will turn on and attempt to boot, but then just sits there with the bottom four buttons lit
7)Next, I have tried the following:
a)Odin JI6 - same result, phone will not move past Galaxy S logo
b)Did a factory reset - then Odin JI6 again = same result
c)Odin stock 2.1 (JFD) with 512 pit = Same result
Please help!
Click to expand...
Click to collapse
Official Instructions for Reverting from a Voodoo Issue:
SOURCE
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.
Click to expand...
Click to collapse
Taken from the Bionix Instruction Page
As a note this will WIPE all the data on your phone except for the external sd card. The internal 16gb card will get wiped. Using ADB I would pull the entire contents of your /sdcard/ to your Computer so that you can restore completely. The command is as follows:
adb pull /sdcard/
Click to expand...
Click to collapse
xxwhitehawk said:
I think its safe to say if you are having a data error then voodoo IS enabled on your phone. You either need to do what I said earlier and flash Eugene's Froyo that does not brick and then downgrade back to JFD OR you might be able to use adb to push a file named "disable lagfix" (no extensions) into the "Voodoo" folder on your sdcard to disable voodoo. You need to disable it before your phone will work.
Click to expand...
Click to collapse
Thank you sssssssssssooooooooooooooo much WhiteHawk. I am now back to original JFD thanks to you. I am more appreciative than you could ever imagine.
clemsonboyz said:
Thank you sssssssssssooooooooooooooo much WhiteHawk. I am now back to original JFD thanks to you. I am more appreciative than you could ever imagine.
Click to expand...
Click to collapse
That is great! Glad to hear everything worked out ok.
Okay. So I pushed Axura final onto my phones internal sd card and booted into recovery mode. The damned Axura copy ( it downloaded properly via google chrome, no errors) had some issue with it and DID NOT install properly. I tried again and again to make it work, did not load flash from voodoo eclair 2.1 to axura which is 2.2.
Now I want to use ODIN and come back.
I get into download mode BEAUTIFULLY using youtubes """Samsung Vibrant download mode; Corntez" .
and then load Odin, load pit file, and the tar/jar file. detected as COM 6 Odin says "added" . then run it. RUNS perfectly. firmware update start; cache.rfs;modem.bin;factoryfs.rfs; and all, and the blue bar finished completely.
Then restarts, "VIBRANT" says "data wiping failed " , everything else succeeds...lots of small writing....restart' VIBRANT" ; then Samsung Galaxy S shiny logo.
Now.....the plot thickens and my vibrant does not move forward. Black, black screen.
If I touch the bottom touch keys---viz, home etc...they light up fine. But the screen. the beautiful screen, remains as dark as Lord Voldemorts heart.
What to do??
I forgot to mention that I moved from a forward port on my thinkpad to an aft port )); and the COM4 in ODIN changed to COM 6 , promptly.
Odin is causing some issues. seems like. Any suggestions and links for newer, better versions of the T mobile stock firmware.????
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
houston123 said:
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
Click to expand...
Click to collapse
Houston we have a problem. Voodoo MUST be disabled BEFORE you flash. There are plenty of info on the board on how to do this. Then ODIN to stock then FLASH. Not all ROM's need a lag fix, some just run smooth!
my phone is doing the same thing but all i did was hit the voodoo button that was available in the oclf app and it went dumb the women counted down and said complete after a while and then it stuck on the vibrant samsung screen. i flash with stock rom and now its doing what this guys phone is doing please help us
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
houston123 said:
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
Click to expand...
Click to collapse
For the dear love of [deity]/self-sufficiency, go read how to solve your problem
(You need to flash Eugene's "froyo that does not brick." Then flash whichever firmware you want.)
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
houston123 said:
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
Click to expand...
Click to collapse
http://eb-productions.proboards.com/index.cgi?board=samsungsgs
I have tried but doesn't work for me. Unfortunatly I too did not disable voodoo before flashing and now I am stuck and can not get into download screen. I guess I will have to take my stuff to a cell phone repair since I have ran out of options.
got eugenes software. Now I am going to try out this:
""""
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!"""
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
houston123 said:
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
Click to expand...
Click to collapse
My opinion on this is not to worry unless it doesn't work. But since you know how to use Odin and your phone can get into download mode okay, it should work.
With the insurance there is a hefty copay. But you should be fine.
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
I need a heimdall image of any type that will get this vibrant up again.
ever since i installed hiemdall, odin does not see the phone when plugged in and in download mode.
I need a recovery image that has all the heimdall files including boot and recovery files. also when i try it without all the files it stops at modem 100% and goes no further (waited 30 min)
i have tried
T959UVJFD and T959UVKB5 with s1_odin_20100512.pit.
neither have the boot and recovery files.
also is it possible to get a file that would put in clockwork mod directly with this process?
*current status is will boot to the Galaxy S GT-I9000 screen and stops. I can get into download mode but not recovery.
ok odin see the phone on a different computer. hiemdall musty have borked my drivers.
i can odin but the images hang at modem.bin
any clues?
^
Check the md5
Remove other usb devices and reboot the pc
Try another usb
Use the cable that came with the phone
Some sound crazy, but all have proven to help others.
mosler said:
ok odin see the phone on a different computer. hiemdall musty have borked my drivers.
i can odin but the images hang at modem.bin
any clues?
Click to expand...
Click to collapse
try this link http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
I have flashed @least 4 times with 100% success....hope it helps you...
I am using both files and cable that i have successfully used in the past.
also the jfd image does not contain boot or secondary boot files. I need these. where can i get them?
mosler said:
I am using both files and cable that i have successfully used in the past.
also the jfd image does not contain boot or secondary boot files. I need these. where can i get them?
Click to expand...
Click to collapse
why do you need those boot files?
deziguy420 said:
why do you need those boot files?
Click to expand...
Click to collapse
He needs those if he wants to do repartition, but you don't need to do repartition.
It's very unsafe to flash bootloaders with heimdall.
Sent from my SGH-T959 using XDA App
i tried to heimdall an eb01 image from a fascinate on to this vibrant. That's what caused all the trouble. Somehow i got into the wrong forum. and that screwed the boot and recovery stuff. This is when it began hanging at modem.bin. I tried the proper JFD image and a KB5 both of which i used before many times since. and i can make no progress.
does anyone have a complete image for this vibrant?
mosler said:
i tried to heimdall an eb01 image from a fascinate on to this vibrant. That's what caused all the trouble. Somehow i got into the wrong forum. and that screwed the boot and recovery stuff. This is when it began hanging at modem.bin. I tried the proper JFD image and a KB5 both of which i used before many times since. and i can make no progress.
does anyone have a complete image for this vibrant?
Click to expand...
Click to collapse
have you tried installing just a bootloader?
wt about thid link
http://forum.androidspin.com/showth...-Froyo-ODIN-Ready-Image-*-Updated-amp-Final-*
ok found and odin'd in a new boot loader from the following link
http://forum.xda-developers.com/showthread.php?t=1117990
it loaded successful and rebotted to the rainbow eye the first time.
now it boots to waiting bars circle makes 1/2 way around and hangs.
EVEN WHEN TRYING TO GO BACK INTO DOWNLOAD MODE!?
ok noob mistake
custom boot loader changed the key combo for dl mode.
got it up. odin'd jfd made it past modem and have a working phone
woot
thanks all