Hey so i have used odin lots of times before and pretty comfortable with the hole process. well computer had a heart attack and needed to be format and blah blah blah. back ups where made stuff like that.
I go to dl new tw rom and i always odin to stock before flashing a rom. so i put my pit file where it goes and i cant find my stupid tar file. i tried to download the t959uvjd.tar file but well the first time said it was going to take 6days and then after trying it a few more times im down to three hours (2.1 stock i know).
I then find after digging that eugene has a 2.2 stock deal. ok so i dl that (which also took forever (20 minutes)) and i tried to go to 2.2 stock. Using odin3 v1 that didnt work, it was hanging up on stupid boot.bin. So after some more digging i find that i need to get odin3 v1.7 and that fixes the hangups. Dl that. went real fast, lol. Open it up and i cant seem to get it to get past connection and it fails out. ive switched usb ports and what not but im wondering if anyone else has this problem or if i should wait the still 3 hours for that gd 959 tar file and go that route, or if there is another link that i can try or a better solution to my problem.
Thank you for reading thew this
EDIT: mods sorry i thought of one other option and it worked. Hate to ask this but would you mind deleting this thread i got it fingered out just fine. Used my 12 pit instead of the 13 pit file and worked first shot.
hi ive searched for a few hours and tried so many different sequences her eon the forums and for some reason i cant get odin3 1.78 to recognize my captivate... otherwise i would have an awesome Cyanogenmod 7 on it.
i rooted it and installed clockwork from the thread "how to install roms" under the dev threads (the big sticky) then attempted to install a custom rom through clockwork and it failed. now my original rom is messed up. i can load into it but android.phone continuously closes...i cant get odin to see my phone thus i cant reflash the original firmware....
yes i have drivers installed.
yes i have the AIO toolbox.
now for some reason i cannot get Odin to recognize my phone AT ALL (download/recovery/loaded). ive literally tried everything i can think of and to be honest i hope someone here can make me look stupid and help me fix it . ive flashed roms before back in the day with my tilt and cliq. but ive been out of the game for a very long time and lemme tell you im completely lost feeling.
im on windows 7 ultimate x86 fully updated.
ill be glad to donate a little bit for some success on just getting odin to recognize because i have everything. its just that stopping me..
You're in the wrong section bro.
http://forum.xda-developers.com/forumdisplay.php?f=703
ah.... thanks..
I bought a T-Mobile Galaxy S T959. When it turns on, it says "Samsung Galaxy S GT-i9000", then the screen changes to "Samsung VIBRANT" I reflashed back to stock using odin, but it still shows the same gt-i9000 boot screen.
Does anyone know how to change it back to normal? So far, I have rooted the device, installed clockwork and flashed to the bionix rom, and installed sgs kernel flasher from the market.
I watched some videos online that showed the kernel boot screen changing after flashing a new kernel through sgs kernel flasher, but I dont know much about kernels or which one needs to be flashed.
Does anyone know what needs to be done, or have any ideas I should try?
Thanks
Well theres nothing wrong with that but it seems like it bothers you so which kernel did u used to odin???
Sent from my SGH-T959 using XDA Premium App
This is happening because the phone in the past was flashed with an I9000 based kernel. Eugene I beleive used to make some back before we had Froyo. I also had that bootup screen for a while. I don't have it anymore.
I believe I lost it through one of the many kernel flashes I have done. Just flash some of the latest kernels. It MAY clear this issue for you though it really is not an issue.
It is just the wrong picture stuck in some folder on the phone. There is no harm done to your phone nor is there anything wrong or defective with it. The only thing is that it may bother you. If it does bother you, go on a flashing spree and flash some kernels and roms. I think sooner or later you will get rid of it without even trying when you upgrade your ROM/Kernel.
Thank you, I appreciate your replies.
I bought this phone from someone online, so it was like this when I got it. Therefore I am unsure of which roms/kernels were flashed onto it in the past. I have flashed many roms, but those only seem to change the boot animation. The kernel boot screen is staying the same. Like I said, I dont really know much about kernels.
Would there be one which you recommend I try that might fix it?
I know its not really a problem, but for some reason it just annoys me seeing it say gt-i9000 at startup.
My ultimate goal is to be running the latest build of team whiskey's bionix rom. I have no clue which kernel I should flash or that would work with it.
Any help or advice is greatly appreciated.
Thank you
Try the bullet kernel.
http://edtdev.com/forum/topic/86-kernelbullet-1420ghz-4202011/
It is the fastest kernel for the Vibrant to date (1.42Ghz STABLE on most phones, outstanding battery life, all features and tweaks). It also has a custom boot screen which MAY replace your I9000 one. I'm saying MAY because I am not fully sure. In either case it is either the best or one of the best kernels for this phone to date.
As for ROMs, Team Whiskey quit Vibrant development around late February. They have moved on the the Nexus S and G2X so I'm not sure their latest ROM is the best. It's certainly an amazing ROM but there may be more recent ROMS which have more features or speed. Choice is yours.
You may try flashing some Froyo kernels from Eugene. Since his kernels likely introduced the I9000 boot you have now, flashing newer versions MAY get rid of it...who knows. Alternatively, there is another option if you are SET on getting it out.
If you flash with ODIN and also check repartition, I beleive ODIN will WIPE everything off the phone completely. Yes, all backups...everything will be gone but it should in theory also take that I9000 with it. It's a bit more risky than normal ODIN but the choice is there if you are set on it. Try the other options first and if you decide to do a repartition, READ on how to do it properly first.
@}{Alienz}{
Thank you, I tried to flash a few kernels and it seems to me like what you said about the wrong picture being stuck in the phone is what the problem is.
I Re-flashed with Odin and did a re-partition as well, but the image is still there. After rooting and flashing the bullet kernel, it still shows the gt-i9000 screen and then it switches to the bullet screen instead of the vibrant one it used to be.
After trying a few kernels, they all seem to replace the screen after the i9000 kernel screen.
Im going to keep trying to get rid of it, but i wanted to thank you for your response as I am one step further now.
Ah. Dumb-stuck image problem then huh. I thought the kernels would flash it right out. Well...you can ask someone above me about how to get it out.
Go to the EDT dev website. www.edtdev.com and join their IRC. See if a developer there can help you out with getting rid of it.
Also try the Team Whiskey IRC chat. They have more devs and people in their IRC that may be able to help. Their chat is located here:
http://webchat.freenode.net/?channels=teamwhiskey&uio=d4
I'm sure someone at those IRC chats will help you out.
try flashing the stock "param.lfs" file through odin
Okay I have had this problem and know exactly how to fix it. What happened was whoever had that phone before you flashed an I9000 gingerbread kernel with I9000 gingerbread bootloaders, that's why it shows that every time. Here is what I did to fix it. I don't know if it has to be done this way, this is just how I did it.
Step 1: download both of these files
PDA:http://dl.dropbox.com/u/23420259/Eugene_JK2_Froyo.tar.md5
PIT:http://dl.dropbox.com/u/23420259/s1_odin_20100512.pit
Step 2: Flash those files through Odin, but make sure you uncheck repartition, as I have read that if you leave it checked while flashing those files you might end up with a hard bricked phone. It will boot straight into recovery after it's finished flashing and will have some errors, that's okay just click reboot system now.
Step 3: Odin back to stock 2.1 like normal.
After you do that and Odin back to stock 2.1 wait like 10 minutes and then flash whatever rom you like. After step 2 though you should be rid of that awful GT-I9000 boot screen. I just Odined back to stock 2.1 to get rid of the broken recovery. I don't think you have to do this.
Let us know if this helped you, so that if it doesn't work someone might have an alternate way to fix it.
Oh also before I forget, I have to give credit where credit is due. Those are files are Eugenes files and I am in no way saying that I developed or had a hand in developing them.
Hey All,
I've been looking for an answer for over a day now, but can't seem to find anything about my specific problem. Here's what happened:
I had flashed to ICS 4.0.3 on my Samsung Vibrant about a month ago and everything was working great until yesterday when I woke up to find the "Encryption Unsuccessful" screen on my phone. I did a little research to find out that there is a fix to this and to NOT reset the phone. So, I took the steps to ODIN the phone back to Stock Eclair in hopes that starting from the beginning again would be easiest way to fix the problem. The ODIN process finished completely fine (PASSED), but now when it reboots, I only get to the first "Vibrant" screen, then it shows the battery and spinning circle icon. Apparently it won't fully reboot. I've tried to ODIN it back to stock several times, and I keep getting the same results. I can get it into download mode and plugged into my computer, but that's about it.
From the posts I've read, it sounds like my phone might still be okay to recover since it does power up, but I can't seem to find a solution to get it fully back up and running.
Any help/recommendations would be greatly appreciated!
Thanks in advance!
Maybe your JFD file is corruption. Check with your MD5 sum if there any error or mismatch.. Just give you an idea.BTW what Odin are u using. I recommend Odin 1.7 I stay away the older Odin or the newer Odin
You are screwed.
Sorry to tell you this but i had the exact same problem and found no solution whatsoever to fix the phone. I finally gave up and bought a Galaxy Nexus. You can try flashing Eugene's Unbrickable Froyo Rom which is flashable through odin as a .tar package along with the pit file. You might be able to fix it but i highly doubt it. I flashed Eugene's rom and got the same results as you described. By any chance did you click "Reset Phone" when the "Encryption Unsuccessful" showed up? If so well yeah your phone is pretty much paperweight as of now...until someone finds a solution. Like you i am also able to access download mode. So i guess there may be a way to fix your phone. Not saying it's impossible...hopefully someone finds a solution soon.
Here is the link to Euguene's rom: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Good luck.
OP, what ROM were you running (specifically. Not just ICS 4.0.3-what is the name of the ROM)? Also what kernel?
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Check here out for a possible solution/workaround.
Replacement Vibrant Coming
Thanks for your recommendations/help guys.
I decided to go to T-Mobile and complain and they are sending me a replacement phone. Apparently it's still under warranty, so it won't cost me anything, and if my data is lost, then so be it...at least all my contacts will still be in tact through my Google account.
Merio - I did NOT hit the Reset Button when I saw the Encryption Unsuccessful screen. Before doing anything I did a little research and I found a forum here on xda that said to not hit that button, and tried to explain a way to fix it using the Heimdall One-Click. Basically it sounded like I'd be flashing back to a Gingerbread ROM. So, instead I just went ahead and tried to flash back to stock Eclair. The results of that were obviously not good.
Woodrube - I was running the Passion 13 ROM (ICS 4.0.3). Was really enjoying it until I got the Encryption "Screen of Death"
I don't know what Kernel it was, actually, I don't really know what a Kernel is...
Thanks again guys. Hopefully I'll be up and running on my replacement phone soon!
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months. Everything was working the whole time. Today, I am browsing through my local news station's app and my phone freezes on me! I pulled the battery and restarted the phone. It boots up fine and gets to the startup screen with the time and the screen lock. I did notice right away that the digitizer screen was not responding to my touch because I could not slide my lock over to get into my phone. I tried a few more soft resets and still nothing. I did notice, however, that the soft keys at the bottom did respond to my touch and they blinked and provided haptic feedback, so at this point I'm thinking it shouldn't be a problem with my digitizer. So I took the battery out then put the phone into recovery and wiped data, cache and dalvik. Then I rebooted the phone once again and still no response to touch at the home/lock screen. I then proceeded to try to reflash the same ICS ROM all over again and that's where the problem started. I can get into download mode and I've already tried to load stock froyo and stock gingerbread, but nothing works. My phone will not go past the "Samsung" boot-up screen. I've already tried several other forums' threads on how to recover a bricked Fascinate, but no matter what I try to load with Odin, Heimdall or anything else, my phone won't load past the Samsung screen. I can get into Download mode and that's it. My phone will not go into recovery using the 3-finger method. When I run odin I get a success message each time. I've even tried to heimdall the files individually and even tried to reload the stock kernel. The other problem I am running into is a lot of the links on these sites are all broken so I am unable to get the files I need. Has anyone else ever had this problem?
Edit: P.S. When the phone is off and on the charger, the grey battery shows the "loading" circle (whatever you call it) in the middle of it, but never converts to showing the green bars moving up and down indicating the battery is being charged. The loading circle is also frozen and does not spin.
im dizzy after reading a few sentences lol...check out my guide in the general section.
droidstyle said:
im dizzy after reading a few sentences lol...check out my guide in the general section.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1238070?
If so, I just did it and it won't go past "Samsung."
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
jawman27 said:
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
I did check re-partition and yes I did load the atlas pit file. Still nothing.
e
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
mvmacd said:
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
Click to expand...
Click to collapse
I used heimdall front end to load DI01 files, I didn't use any commands. Also, I was just referring to "Unbrick your samsung fascinate" threads on other websites. A lot of the links I found were outdated or broken.
yea unfortunately not many guides have working links these days...Mine is about the only one left that is kept up to date. Im very suprised a full odin session did not fix your issues. One thing left to try is to odin a older stock package like DL09
Found here:
http://forum.xda-developers.com/showthread.php?t=1526488
Just tried pushing the DL09 file in odin AND in heimdall and neither worked. I still get stuck on the "Samsung" boot and it goes no further. Can't even get into recovery....
I think I truly have a brick...
kinna long shot
but why not try a different PC and a new or different cable.
believe me a faulty cable did me in, a week back and i was sure at the time that my phone is gone, but then it wasn't as bad as the impression i am getting from your description.
all the best with this , and hoping that something solves this issue.
god bless
haoleflip said:
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months.....
Click to expand...
Click to collapse
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
kduffman said:
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
Click to expand...
Click to collapse
I have a blue recovery [3.x, voodoo], here it is if the OP wishes to try it.
[Use Heimdall and select recovery]
cwm3_voodoo-blue.bin http://www.mediafire.com/?4ls06x8gha88vtp
cwm4-bml-i500-fascinate.bin http://www.mediafire.com/?2ny1ql66yh69bn3
35c31418dbe9a9db70de954cdf7369ef cwm3_voodoo-blue.bin
05f3e376ca697fd0fb8700dea05254aa cwm4-bml-i500-fascinate.bin
I threw in an extra 4.x cwm for good measure, lol. [I saved these in a folder in case I ever needed them..I was going to delete the folder since I upgraded to THS ICS rom (build 7.1), but I decided not to delete them for some reason]
it seems OP sounds like he knows what he is talking about, but lets start simple.
Have you tried going all the way back to 100% stock?
In droidstlyes FANTASTIC guide
do section 5, perhaps try with out repartition or the atlas....that has worked for me in the past.
I know on my THS ICS 7.1 build i had a "sleep of death" (wouldnt wake up) and i was lazy and did the 3 finger salute and it would ONLY boot into CWM. a battery pop would have been fine but like i said i was lazy. i had to Odin back to stock in order to re-flash everything. [luckily i had a nandroid from a few days earlier]
Good Luck
Edit: I have never seen or heard of a fassy that CAN get into Download mode and not be recovered to 100% functional.
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
OP, can you post the md5sums of the files, along with the filenames that you are using in Odin/Heimdall?
thanks
Well, I ended up getting a droid bionic from a friend, so I will turn this fassy into a project phone. If I can get it to work I will sell it or keep it for backup. Anyway...
I have not tried the older blue recovery yet. I will try that when I get back to my computer. It seems like I've gone beyond anything I've ever had to try with this phone. I read on one thread that if odin did not work, keep trying heimdall over and over until the phone boots up. I must have tried at least 8 times on one run. It still won't go past samsung screen. I can get into download just fine. No matter how many different cwms I try, I can't get into recovery using the three finger method. Im pretty knowledgeable when it comes to this stuff and I didn't flash the wrong rom or kernel or anything like that. I was running smoothly on an ics rom until my phone froze. I did have it overclocked with ns tools, but not at the time the phone froze. I honestly don't think its hardware related, but merely a glitch in the software or a bad kernel that does not want to come out? I have no clue....help me revive this baby lol...
Sent from my DROID BIONIC using Tapatalk
jawman27 said:
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
Click to expand...
Click to collapse
I've tried different pit files from different threads. Even the one from droidstyle's thread. I've also tried different versions of the following stock files from different "known" and trusted sites: DI01, DL09, ED01, EB01, EH03, CM7, CM9 other ICS roms and different kernels that suit each both voodoo and non voodoo. And excuse my newbness on the terms, but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
haoleflip said:
... but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Bootloaders can be flashed in Odin the same way a ROM can. A bootloader is the rudimentary software that gets the other software up and running. When Glitch's kernel started requiring Gingerbread bootloaders for complete functionality, a lot of us realized that just having GB didn't mean you had GB bootloaders.
http://www.mediafire.com/?fqojvsynkff93hc
Hopefully this link will work. It's certainly worth a try. It doesn't seem like you have much to lose. I'd recommend flashing it the exact same way you do a ROM. There's a bootloader section in Odin, but most people avoid it. Good luck.