yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] jrafael:
@op

Check ezodin over gt9000 dev forum. I liked better than regular odin
[Vibrant Android Development] hitman818:
When I downloaded the bootloaders it showed .md5 after .tar, should we rename so it could show just tar, or is it okay that its their?
[Vibrant Android Development] adyscorpius:
.tar.md5 is a known extension that enables ODIN to first verify the md5 hash and then auto extract from the tar file. There's no need to do anything to the files or change anything to the extension... You'll be good with that extension on... :)
[Vibrant Android Development] adyscorpius:
I've replied to all queries I believe so I'd personally request no questions over PM. Please rather ask here for the benefit of all reading it.

Thanx!!!
[Vibrant Android Development] lldtbll#teamwhiskey:
Bump

Sent from the always morphing, always changing, Vibrant Galaxy.
[Vibrant Android Development] adyscorpius:
Yea i know, it's something I too was wanting to bring out long time back... I really don't know if I should make it as easy as a flash... Considering that we do have people hitting the thread and not realizing what they're doing after they've already done it. And unlike other wrong flashes, which are curable, this one won't be.

I have no issues releasing it out, its just that I'm skeptical of its outcome.

Need some more time deciding it.
[Vibrant Android Development] Shazmania:
How am I to flash these bootloaders if I can't odin or get to recovery? I currently have simply honey installed
[Vibrant Android Development] adyscorpius:
Please don't try to flash these if both the above things ain't working for you... You may want to return to JFD stock, or flash Eugene's Froyo that doesn't brick or a similar thing...
[Vibrant Android Development] Shazmania:
How can I return to stock... This is terrible :/
[Vibrant Android Development] viralbug:
This is exactly what I was gonna post. People see some CWM flashable file, they download and then flash it straight away without reading anything. I bet some don't even know what they're downloading. :p

Great work with the bootloaders. I'll come back here if I decide to flash a GB rom.
[Vibrant Android Development] amandadam:
You mean to say you've never used odin?There's nothing terrible about it,except no gps,which has sucked from the beginning,for many.

I assume you can get into download mode and use odin,or

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

Edit:Sorry,wrong section.I guess you mean stock bootloaders.Use odin and flash the froyo bootloaders,as per OP.
[Vibrant Android Development] adyscorpius:
Terrible !! Well, what's terrible is that you're playing with the most risky part of your phone without knowing what it does or how to return to stock.

What even worse for that matter is, you haven't yet read the OP, or if you have, and maybe you still didn't get how you can return to stock, you're one of those flashers who just flash anything and everything that has a jazzy title bar !!!

Coming to your solution, assuming you've managed to get GB bootloaders on your phone, do the following, exactly in the same sequence.

1. Turn off your phone.

2. Press the Volume Up + Power Button

3. You should see a Yellow Download mode icon on your screen.

4. Connect to USB and open ODIN on your PC.

5. If it shows as connected, uncheck all tick boxes, and open PDA, and select the Vibrant_froyo.tar.md5 file.

6. Click on flash. Once its complete, disconnect the USB and restart your phone by long pressing the power button for around 8-10 seconds till your phone reboots.

Please do not flash these bootloaders, or call them terrible if you don't know their use or rather expected GPS to start working or something of that sort. Trust me, not even God can help GPS on our phones, I'm just a man with a lot of sins. :D
[Vibrant Android Development] Dan_Brutal:
I flashed the ginger bootloaders and everything went smooth. Scariest 10 second flash of my life. Thanks for your hard work!!:D:D:D
[Vibrant Android Development] lotherius:
EDIT: My Problem lay elsewhere. Complaint removed.... n/m on this thread.
[Vibrant Android Development] adyscorpius:
Please don't use Heimdall for Bootloaders

Hey everyone...

I managed to brick my phone thanks to Heimdall... Even though its repaired now, had to give it for a RIFF-JTAG Repair, costing me 20$ (Its pretty cheap here in India), but yes, the problem lay in the fact that Heimdall reboots the phone, no matter what, even if its a good or bad flash...

In my case, it caused the phone to reboot even when the bootloader flash was bad. And tada, a phone that was a paper weight.

So yes, request you all to not use heimdall for bootloaders, unless anyone has a solution to that sort of a problem !!
[Vibrant Android Development] tennandcoz1:
Hey Dan lets go Yankees.haha

sent from a Ginger vib
[Vibrant Android Development] Dan_Brutal:
Boooo!!!
[Vibrant Android Development] RobZarzecki:
Ha good one.. It is a very quick flash for those wondering.. Been using since day one. Still no problems
[Vibrant Android Development] adyscorpius:
Feels good to hear that... I might up a 2.3.4 ROM soon, if time permits and if I don't go on my bike tour which would mean a 20 days break from a computer...
[Vibrant Android Development] thechadhall:
this is awesome! i didn't have any issues getting into download or recovery, but i like the key mapping better. great job!
[Vibrant Android Development] Kwaii49:
Has anyone on the miui.us aosp version tried this?

I understand MIUI is 2.3.4 ( from what it says on my phone) which is gingerbread, so did any try the gingerbread boot loader?
[Vibrant Android Development] Whitehawkx:
I was going to vote, but there's no "Roman and Cmenard made me" option. :(
[Vibrant Android Development] Dan_Brutal:
How about Dan Brutal made you:D
[Vibrant Android Development] adyscorpius:
I wish it was like that, or maybe I'll just add, Whitehawkx made me... :P
[Vibrant Android Development] RobZarzecki:
What? 20 days? Bike tour. Well I hope you have a working gps on your vibrant . Oh wait.... Nevermind. Lol
[Vibrant Android Development] AngryDinosaur:
do i need to be on a GB ROM to flash?

or can i be on a froyo rom and flash the GB bootloader?
[Vibrant Android Development] adyscorpius:
You can flash from any ROM... However, avoid on CM7 and MIUI, I didn't get very good results there...
[Vibrant Android Development] adyscorpius:
Yea, its a trip from Delhi to Leh, Ladakh, in India... 20 days up and down, 3500 kms and totally rough broken roads over hills with snow and pebbles for around 2000 kms of it...
[Vibrant Android Development] GYM_RATttt612:
Works perfectly if done correctly! Quick and painless. Thank You!!!!!
[Vibrant Android Development] RaymondPJR:
bootloaders

Are you still toying with making the bootloaders cwm flashable? If I can avoid my Windows partition, I will. I don't think there is a version of Odin for Linux, but it's time to find out.:)

EDIT: NVM, I see the Linux alternative is Heimdall.
[Vibrant Android Development] viralbug:
OMG!! That's totally awesome man!! Have loads of fun dude. I've always wanted to go to Laddakh so badly. :(
[Vibrant Android Development] :
My only question is ok so I flash a gb rom put the 2.3 boot loader via odin but then when I want to go back to 2.2 do I flash vibrant boot loaders then flash?
[Vibrant Android Development] RaymondPJR:
bootloaders

Of course I would mess up. I have the 'possible outcome' but the phone is stuck on downloading. Disconnecting and restarting/reflashing doesn't do anything. The phone remains stuck on downloading. Time to buy a jig? BTW, I watched your video (which has no sound), and in it you do not have 'auto-reboot' unchecked. This contradicts you instructions.:)

EDIT: Well, the phone is rebooting, so I'll give it another shot.

EDIT2: Odin said 'pass' this time, we'll see when I flash Simply Honey Gingerbread.

EDIT3: It did work, no one warned me I'd lose my TW-GTG launcher!:eek:
[Vibrant Android Development] AngryDinosaur:
so if i use the GB bootloader i can still flash any 2.2 roms correct?

like Project V or Bi-Winning?
[Vibrant Android Development] adyscorpius:
I haven't unchecked that because I knew what I was doing... Its a safety thing I suggest, not otherwise.. If its a bad flash, atleast you might just be able to reflash without having phone that reboots and can't find the right bootloaders to load, it'll become a brick... Also, it adds time to the Video, and I didn't want it to be so long and boring !!!
[Vibrant Android Development] AngryDinosaur:
i have a galaxy s I9000 boot logo and a vibrant boot logo

did i do something wrong?

can i Odin the bootloader twice? just to make sure i did it right?
[Vibrant Android Development] adyscorpius:
Have you ODIN'd to JFD or in any ways updated the param.lfs file ???

If yes, then reflash the GB bootloaders, you'll be good to go... There's no problem in having I9000 boot flash, but if you need, you can reflash any of the bootloaders you need and it'll be back to Vibrant !!!
[Vibrant Android Development] AngryDinosaur:
how do we reboot after odin says pass?
[Vibrant Android Development] adyscorpius:
Long press the POWER Button for 10 seconds... It'll reboot...
[Vibrant Android Development] AngryDinosaur:
thanks man

i flashed it

thought i messed up

odin to JFD

re-rooted, then flashed bi winning v2, still seeing I9000 boot logo

still ok at this point?
[Vibrant Android Development] adyscorpius:
Reflash the GB bootloader again... It'll all be fine...
[Vibrant Android Development] AngryDinosaur:
This is quite stressful
[Vibrant Android Development] AngryDinosaur:
Cool I'll do that tomorrow

thanks a lot man
[Vibrant Android Development] mainevent3405:
My question as well.
[Vibrant Android Development] tennandcoz1:
Why would you want to go back to froyo brother its a thing of the past.see ya, good bye.with gps just about fixed and bootloaders up now with this easy method.I just do not get it. but good luck to ya.
[Vibrant Android Development] adyscorpius:
I won't answer that. Please read the FAQs...
[Vibrant Android Development] mainevent3405:
You guys are funny...Lol. Relax, it's really not that serious dude, it's only a phone. I got the answer scorp, no worries, roflol. Thanks for your help!
[Vibrant Android Development] adyscorpius:
:) Cool man... Hope you don't take it as RUDE... :P
[Vibrant Android Development] Demetris:
I was on Cyanogen nightly 25 and flashed froyo bootloader, nothing i did couldnt bring me back to working phone.

Phone keep booting to recovery.

I Reflash stock.

Problem is reproductive you can try it and see your self, dont know the cause as of today.

No MUI no nothing, phone was jdf and went straight to cyanogenmod.
[Vibrant Android Development] adyscorpius:
A small technical thing, hope it helps...

Short Answer: flashing BML reading bootloaders over MTD partitioning CM7/MIUI will make the phone bootloaders not read the system/data/cache partitions. Hence the reboot to recover.

Long Answer: CM7/MIUI use the MTD partitioning while Samsung ROMs use BML... When you replace bootloaderd after installing CM7 or MIUI, well, you just give it bootloaders that cant read the MTD partitions created by the ROM...

If however you flash the bootloaders first and then the ROMs CM7/MIUI, everything is fine again...

EDIT: Did you read the FAQs ?? I just saw, I already have posted it on point number 9, edited on 13th June, that you will face that issue.

Anyways, just flash the bootloaders first after flashing JFD, and then move to CM7/MIUI.
[Vibrant Android Development] z3NN9:
Fixed phone and was able to flash boot loaders using .pit file.
[Vibrant Android Development] kwes1020:
Ok. Well I finally decided to try this out. Everything was going well. Following the instructions exactly. md5 matches and all that good stuff. I started the flash it has been hung on sbl.bin for about 5+ minutes. Is it a bad flash or something? What can I do to fix it, if it is?

EDIT:

Been almost 20 minutes now and same thing. It is still stuck on sbl.bin and has not gave a pass or fail. I really dont want to brick it if I havent already lol. So I am gonna leave it like it is till I can get some advice...

Edit2: Managed to save it luckily. Not sure if I want to try it again lol.
[Vibrant Android Development] adyscorpius:
You are scaring me... Lol

Re download the files, reboot your system, ODIN to stock, then follow the steps... if odin is taking so long, something's wrong with the computer. Try giving it admin rights...
[Vibrant Android Development] adyscorpius:
Brick? Is it the "phone ! Computer" screen???
[Vibrant Android Development] domtru:
Yep I got the phone exclamation computer, tried to download Froyo bootloader but had auto reboot checked...kept getting failed, now Im stuck on phone ! computer screen. Any help? I figure that after a year of doing absolutely everything to this phone I may have finally truly bricked my phone. Wow. Im stunned.

:o
[Vibrant Android Development] tennandcoz1:
Not for nothing I had auto reboot checked.worked flawless.the reason I had it checked was in the video it was checked.good luck

Sent from a ginger vib with some honey
[Vibrant Android Development] pvspencer22:
I love that people still think this is a brick. With that screen just use Odin as if you were in download mode.
[Vibrant Android Development] adyscorpius:
Two things... One, its definitely not a brick. Cuz literally, bricks dont show anything on screens... It can be saved.

Secondly:

If you get Vibrant, and then that Phone!Computer screen, then its a bad kernel/recovery. You just need to enter Download using the three button combo or maybe the Gingerbread combo in the OP, and flash JFD using ODIN, and check repartition.

If it directly goes to that screen, use the button combo's again and use ODIN to reflash Eugene's Froyo that dont brick, and your phone will be back to life. Do not use repartition with this. It does it automatically I believe...

EDIT: If you have the download JIG, its best to use that, gets you to download mode 99.9% of the times... .1% it won't, and that's when you have a brick !! :D
[Vibrant Android Development] domtru:
Three button combo into download mode into recovery! Odin reflashed froyo bootloader which was a success, for some reasonni couldn't Odin the froyo bootloader. But anyway, rainbows gone and I'm able to get into recovery! Wheeeeeeeeeeeew!
[Vibrant Android Development] adyscorpius:
Just reflash Stock JFD using ODIN, and stay away from bootloaders till you read everything in the OP, and have stable USB connections, updated drivers on your system and you know what you're doing...

That is exactly why I don't want to create CWM zip files... I know people will screw their phones...
[Vibrant Android Development] kwes1020:
Idk why it got stuck there. I think it was because cwm was not loading right or that version of odin didnt like the file. When it got stuck there I unplugged and the pc wouldnt recognize it. So i rebooted got the phone!pc screen, flashed jfd with odin, and it was back alive.

After that I got a newer version of odin and reflashed the gb bootloader. It failed I unplugged and restarted odin flashed again and it was all good after that.

Thank you I really appreciate it!
[Vibrant Android Development] s1lenz:
I've read the OP 5 times and I just want to make sure I understand what I'm doing..

To flash a gingerbread rom coming from stock, I would first flash the gingerbread bootloader in odin with auto reboot unchecked, then without rebooting flash the gingerbread rom of my choice? I'm assuming the phone will not boot properly because if I rebooted after flashing because i would have a gingerbread bootloader with a stock froyo rom?
[Vibrant Android Development] mainevent3405:
Deleted...wrong forum
[Vibrant Android Development] adyscorpius:
Okk, rebooting is kept unchecked so you are sure of being in download mode when the OdIN flash is successful or a failure.

You basically should be on any ROM, not necessarily 2.3, and should enter Download mode, flash the bootloaders, and reboot using the long press of power button. GB bootloaders work on all Samsung ROMs, not so successful with CM7/MIUI...
[Vibrant Android Development] RaymondPJR:
bootloaders

That's why I mentioned that a page back. It contradicts the instructions and someone who doesn't know how to recover might get trapped.:)
[Vibrant Android Development] adyscorpius:
Auto-reboot enabled or disabled will not cause any bricks... It was checked in the video because I didn't want to add those 10 seconds of reboot time twice to the video. Also, it worked with auto-reboot for me, as the video shows.

However, when I have put the step by step method of flashing in the OP, I don't see a reason why the video is taken as a guide to methodology. It is only to show how the new bootloaders help with the Rainbow, nothing else.

PLEASE DON'T DO STUFF TILL YOU KNOW WHAT YOU DO OR HAVE ASKED ME.

I WON'T BE RESPONSIBLE FOR THE PHONES THAT BRICK, CUZ YOU DID SOMETHING WRONG AND THEN THOUGHT OF ASKING HOW TO CORRECT IT.

ASK ME, BEFORE FLASHING...
[Vibrant Android Development] adyscorpius:
Ohh, n ya, even though with auto-reboot, it will just reboot perfectly almost 90% of the times, but consider a scenario of a single bad flash, and while you're looking at the computer screen, that says "FAIL", your phone reboots into nothing but a black screen. You would realise that had that single tick been kept unchecked, you could still have managed to reflash to a successful bootloader install.

Hope you understand now, as to why I ask you to keep auto-reboot unchecked.
[Vibrant Android Development] z3NN9:
I just wanted to post again to say I was able to recover my phone! Eventually managed to get the phone back into download mode and flash JFD.

I found that the only way for me to get the boot loaders to flash WAS TO INCLUDE the .pit file. Without this I kept getting stuck at SetupConnection before that and ended up with a soft brick.

Just wondering if you may actually want people to choose a .pit anyway to insure they don't end up soft bricking like I did?
[Vibrant Android Development] RaymondPJR:
bootloaders

Odin gave me a pass a few days ago, problem is when I test the button combination to get into recovery, it gives me the menu options. The combination of the 'volume up+power button does get me into download mode, though. Any other way to test if it really did flash properly? I'm on Simply Galaxy 2.8 Final and want to flash directly to Simply galaxy Gingerbread.:)
[Vibrant Android Development] adyscorpius:
The second BML/STL partition on the phone already contains the PIT information, hence I didn't include that in the steps... Did you have repartition checked without the PIT file selected???
[Vibrant Android Development] z3NN9:
Negative, I repeatedly read the instructions and followed them to a T. Even after recovering through Odin, I tried it again without the pit file and got stuck. The next time I loaded the .pit and it ran through in about 10 seconds.
[Vibrant Android Development] NinoAl:
I just finished flashing simply honey 3.8 on my other vibrant

..after setting it up i tried to flash the gb bootloader thru odin....while it was flashin my vibrant went to a black screen....and now everytime i connect to pc or try to turn it on i get this black screen with a sign like this phone>> ! <<PC...can someone help me please...what else can i do?

Sent from my Simply galaxy 3.6 Vibrant
[Vibrant Android Development] domtru:
Fair enough. I figured it out prior to getting back online XDA. I'm by no means a noob nor am I an expert. I appreciate the support. Thanks!
[Vibrant Android Development] z3NN9:
When this happened to me last night I ended up having to Odin back to JFD (lost everything on phone) and start over :P

Good thing is its not totally bricked!
[Vibrant Android Development] RaymondPJR:
bootloaders

Nino, a word to the wise. Always read the last few pages of a thread. Someone with that problem just posted about it a few pages back and I do believe Asclepious gave a response. Be calm, it will all be alright.:)

EDIT: Sorry, Adyscorpious.
[Vibrant Android Development] zoid_99:
I also have had some weirdness flashing this. The first time I flashed everything seemed to go ok but I didn't get the correct image on boot. I decided to flash again because I'm either stupid or stupid and then it locked up and I had pull the battery. At this point I wound up @ (Phone ! Computer). To get back to download mode I pulled the battery and held the up volume key while pressing power which makes me think I have the new bootloader. I proceeded to flash JFD and everything seems ok except the spash screen is i9000 for a split second and then goes into Vibrant. Maybe this is normal? Anyway I'm about to flash honey and maybe everything will be ok...
[Vibrant Android Development] adyscorpius:
Yep... Just a page or two back... Thanks Raymond.
[Vibrant Android Development] adyscorpius:
Dont take it offensively man... We're all here to build our Vibrants into awesome phones... Given that, I'll suggest, repartition ODIN to JFD stock, then flash GB bootloaders and then the ROM of your choice. Follow the instructions written, I'm sure this time you'll do it... :)
[Vibrant Android Development] adyscorpius:
Reflash GB bootloader package. The temporary i9000 splash is a known issue after JFD and in the FAQs...
[Vibrant Android Development] geosa:
It looks like I bricked my phone too. Tried everything...but still stuck at phone-!-computer without vibrant. tried the odin but stuck at cache.rfs for long time.... pls HELP. AND ALSO WHERE CAN I GET Eugene's Froyo ?
[Vibrant Android Development] NinoAl:
thats just exactly what happened to my phone earlier...im back to stock now...im going to flash simply honey 3.8 via odin...then flash the gb bootloader...but this time im gonna use the 512 pit file...last time i flashed the gb bootloader on my other vibrant i left the auto reboot checked and just the .tar file...i wonder if that has something to do with it...cuz i unchecked everything when flashing this time and it wouldn't flash properly twice...
[Vibrant Android Development] adyscorpius:
If you think auto-reboot helps you in flashing the bootloader, you may do that... I've always used the method I have in the OP without fail...

You may use the .pit file if the pit info on your phone seems not to accept the files...
[Vibrant Android Development] CBung:
Very awesome thank you! Fixed my rainbows after my first ever GB rom (SH3.8).... Is it a difficult process to put a custom image in this baby?
[Vibrant Android Development] RaymondPJR:
simply galaxy

No problem, it's been that way ever since I started reading the threads and I'll never get it. (why people don't read a little first). Anyway I found out why I could not get into recovery using the volume down+power button thanks to a hint from EB. It was because I never flash anything without being on the charger. Once I unplugged, things went as EB said they should. Please let other bimbos know if they do the same and somehow miss this post. Sorry for wasting space with my post on that, lol.:)
[Vibrant Android Development] adyscorpius:
There's something regarding the image size and resolution there... Need to get it right to not brick... Will read more on that and revert back to you on that... :)
[Vibrant Android Development] NinoAl:
i redownloaded the .tar file and flash it with auto reboot and it worked...maybe the file i had previously that i used to flash with my other vibrant got corrupted...or the auto reboot did help...i don't know...but im happy everything is working now =) thanks guys
[Vibrant Android Development] vazovskiiii:
<ID:0/005> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> MD5 hash value is invalid

<OSM> Vibrant_GB.tar.md5 is invalid.

<OSM> End...

can you tell me what to do?