yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] jaikat:
gb bootloaders are for gb roms, and the ones in the OP are backword compatible with froyo roms.. meaning you can install both gb and froyo "samsung" roms if you have the gb bootloaders flashed..

but: miui and cm7 need froyo bootloaders (i think)

as for simply honey, if its a a gb rom, then you need the gb bootloaders.
[Vibrant Android Development] ameedi600:
Is it hard to flash the bootloaders and if I were to flash them, then I would be able to use froyo and gb roms. Without having to Odin back to 2.2 to get froyo roms, am I right or not? Thanks for your answer
[Vibrant Android Development] adyscorpius:
Please read the first couple of posts...

To answer your question, its not tough. You just need a stable USB connection to your PC...
[Vibrant Android Development] ameedi600:
You didn't answer my second question, please and thank you
[Vibrant Android Development] adyscorpius:
I shouldnt have answered the 1st one too... Read the OP...
[Vibrant Android Development] jcc332006:
Dam Scorp! LOL! You're true to form. LOL! Can you flash it for me and stick the phone and rom back to me thru the computer.. PLEASE PLEASE!!! :D:D
[Vibrant Android Development] adyscorpius:
I would, if your bandwidth supports 3 TB/s... The only this I know that does it is an ejaculation... Anything less, and phone will fry... Lol

Haha

How have you been doing mate? I got an SGS 2... Been rocking it well... Amazing stuff... So Vibrant is with my younger bro, who just lives CM so much, he doesn't need my bootloaders at all... Hehe
[Vibrant Android Development] jcc332006:
Man i'm good. You got the SGS2 that's hella cool! I had an international version in my hands about a month ago and had put the $660 in their hands until they told me I could only get 3g. Hell I took my money and walked out. LOL! I'm waiting on hercules which is reported to be dropping around the end of august. I'm always looking at the SGS2 forum and development is really nice. I'm about to test the booloaders for a possible 1st Toxic Gingerbread release. Getting kind of tired of Froyo, but it's just so stable. Other than that man it's all gravy. Good to see you still hanging out. Cheers!:)
[Vibrant Android Development] adyscorpius:
Frankly, I can never leave the SAMOLED. Its so freaking awesome...

And gettin CM support with almost 4 devs getting SGS2 for free from Samsung, and also the sales it got, even without the American markets, it was an obvious choice... Getting 2 days of battery where I got just one with Vibrant and similar usage...

So its amazing... :)
[Vibrant Android Development] rush_ad:
then how come OP mentioned this in OP? May be I am not getting a joke....

"Flash these Gingerbread Bootloaders and there you go, no issues on Gingerbread except GPS!!"
[Vibrant Android Development] adyscorpius:
Well, I haven't been updating the OP since I ain't using this phone anymore... The OP was last updated when GPS was an issue with Gingerbread.

But yes, everything works now... However, you'll need to be back to Froyo bootloaders to get external sd working on CM7/MiUI...
[Vibrant Android Development] geoffcorey:
You're reading that sentence wrong. It reads "there are no more issues now, excluding gps since we don't have any leaks to get the gps binary needed for our gps to work", but since this thread was made, a lot has changed.
[Vibrant Android Development] chrystal0925:
Ok i tried to revert back to froyo installed like always says passed but all i can get is to the bootscreen then its black n buttons light up trying to get back to cm7 but ive tried everything any help or sol??
[Vibrant Android Development] geoffcorey:
Odin jfd, Odin bootloaders, flash CM7. In that order.
[Vibrant Android Development] adyscorpius:
If you use ODIN partially over CM7 or MIUI, it wont work, like you did to flash froyo bootloaders. Hence you couldn't go into CM7.

CM7 uses MTD partitioning while Samsung uses BML. So Odin back to stock, then reflash CM7 or MIUI and don't change bootloaders while on them...
[Vibrant Android Development] chrystal0925:
Ok its a good thing I have two vibrants.. But I was only able to odin to jfd after installing a kernel,with voodoo let it repartition etc.. Then reflash stock again.. I followed steps originally, I odin to jfd flash boot but something was still in there..

Anywho if it helps anyone..
[Vibrant Android Development] adyscorpius:
I couldnt understand what you mean... Whats wrong?
[Vibrant Android Development] chrystal0925:
Oh I just mean I got it finally I had to install a voodoo kernel repartition then Odin jfd... I meant I think it wasn't working cuz it seemed like something was still left in system and not allowing it to work..
[Vibrant Android Development] adyscorpius:
Whenever you ODIN to jfd, you should repartition if there's alot of corruption on the drives...
[Vibrant Android Development] Demetris:
i have a feeling that your brother will need your bootloaders soon enough ;)
[Vibrant Android Development] adyscorpius:
Lol, nah, he is happy shifting between CM7 and MIUI...
[Vibrant Android Development] Demetris:
Lol, Cm supports your gb bootloader in the next to come nightly ;)
[Vibrant Android Development] chrystal0925:
I did like 5 times lol I spent 5 hours trying to get that vibrant back to life.
[Vibrant Android Development] strictlyrude27:
Now that CM7 supports the GB bootloader, is there any reason to switch to it (aside the keymapping)?
[Vibrant Android Development] austindkelly:
I have tried to use the VIBRANT STOCK (FROYO) BOOTLOADER but it fails the hash check in odin. I tried from both download locations.

Any help on this would be appreciated.
[Vibrant Android Development] adyscorpius:
Just redownload the file. That's all I can say. Or if you're sure the file is intact, remove the .md5 in the end by renaming it, and try flashing...
[Vibrant Android Development] cavinsays:
The phone-dotted line-exclamation point-dotted line-computer icon came up after I quit Odin and restarted my phone when it hung at the first part of flashing. Before, at least I thought, this meant I had to get back to download mode but after trying and trying to get back to download mode, I just decided to open Odin after my last attempt to see if it was recognized. It was. So don't panic if you see the same thing.

However, I might panic if my phone doesn't leave the green Android man dancing in space soon...

Edit: As hoped and expected, after using every insult in the book on him, the green Android man finally got the message and let me get back to my phone. God he is such a creeper. I had to him blocked on Facebook.
[Vibrant Android Development] dublued:
I seem to be having some trouble.

I have just recently installed the latest version of Simply Honey. When I tried to flash some add-ons I learned that I was unable to see the recovery screen and would need to flash the GB bootloader.

The problem I'm having is that I can't successfully get the phone into download mode. I power off the phone, then power on by holding the power button along with volume + and volume -. The screen is blank but ODIN detects the connection.

I thought that this would be download mode since I'm not supposed to be able to see anything on the screen. When I try to flash something ODIN gets stuck at

<ID:0/005> SetupConnection..

until I reboot it. Any suggestions?

Edit: Holding down the power button doesn't bring up menu for rebooting into recovery or download mode as the video shows.

Edit 2: I got it to work. I went into rom manager. Told it to boot into recovery. Once I got into recovery it was the rainbow screen. At that screen, i pressed teh combination of volume up voluem down and power button. It got me into download mode. I'll leave this up in case someone else has the same problem

Edit 3: Read the post directly below this. I don't want to be responsible for bricking your phone.
[Vibrant Android Development] o0stryxs0o:
^^^^You also put your phone into download mode by holding the Volume up and down key and plugging in the USB cord connected into your computer not by holding the power button also. It's extremely important you know what you are doing as the OP says because you can certainly brick your phone this way!
[Vibrant Android Development] ameedi600:
Do I have to flash all the files that are in the op?
[Vibrant Android Development] adyscorpius:
No, just the ones you need...
[Vibrant Android Development] ameedi600:
Nevermind, i got it to work and also the vibrant gingerbread bootloaders did not work for me. I had to use the custom bootloaders for it to work. The one with the android logo. But as long as it worked then im good. Lastly would miui work with these bootloaders
[Vibrant Android Development] ameedi600:
I want to know if miui would work with the gb bootloaders
[Vibrant Android Development] adyscorpius:
Yes it will... It works with CM7/MIUI and all stock Samsung ROMs...
[Vibrant Android Development] ameedi600:
Alright thanks for all your help
[Vibrant Android Development] vibrant808:
I just flashed the froyo bootloader on miui revamped. Stuck in a recovery bootloop. Anyone got any ideas how to fix?
[Vibrant Android Development] adyscorpius:
If you read the OP, you will see you're not supposed to flash on CM7/MIUI. ODIN back to stock JFD, then flash Froyo bootloaders.
[Vibrant Android Development] sada23:
Hi,

I am a new to Vibrant and and trying different ROMs. I flashed the Custom GB bootloader on Biffmod V1.3 and since then, I am not able to flash Jetpack, Simply honey ot Juwe ROMs.

If you could advice me what to do if I need to flash other ROMs.

Thanks
[Vibrant Android Development] chrystal0925:
U should read the op of the rom your flashing not all are able to flash over one another like coming from an aosp like CM7 U CANT FLASH simply honey straight over it u shouldn't be messing with gb bootloaders unless the rom requires it.. best bet odin to jfd then rom of choice
[Vibrant Android Development] sada23:
Thanks a lot. Will try that.
[Vibrant Android Development] burn0u7:
badass! No more gay rainbows. huge thanks!
[Vibrant Android Development] Jasonhunterx:
Cm7 is non touchwiz so it converts everything an u can't covert back only way is to Odin then flash other roms
[Vibrant Android Development] adyscorpius:
Its not about touchwiz. SGS2 runs touchwiz and still you can shift between CM7 and Stock ROMs.

CM7 is based on MTD partitioning and Samsung ROMs on BML. Hence once it converts to MTD partitioning you need to use ODIN to convert back to BML.
[Vibrant Android Development] cezzarmicu:
Hi,

Sorry if this has nothing to do with the op, but I am on miui right now. And since it's on a different type of partition, will I have to check repartition if I were to odin back to jfd? Or will it not be necessary to repartition?

Thanks
[Vibrant Android Development] gamikzone:
yes its better to repartition when going back to stock, if ur going odin to a gb rom then it is not
[Vibrant Android Development] strictlyrude27:
FYI, I was able to flash the GB bootloader via Heimdall 1.3.0. Unlike my last experience, it was quite smooth! Literally 3 seconds (if you don't include the hesitation I had before hitting <ENTER>) using this command:

heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --verbose

So if you're hesitating to use heimdall to flash, upgrade first to 1.3.
[Vibrant Android Development] t1h5ta3:
bump to save from having to search
[Vibrant Android Development] M5devil:
I was on GB bootloader and flashed back to froyo bootloader, I see a splash screen of I9000 for a sec before it back to Vibrant screen. How do I fix that? Also I am not able to enter into recovery with 3 buttons.

Thanks

UPDATE:

Reflashed froyo bootloader, all good now!
[Vibrant Android Development] zul8er:
This is linked in the Vibrant Bible ;)
[Vibrant Android Development] zul8er:
Just flashed the GB bootloader. No if i want to flash the GB boostloader with the custom flash screen, I can reflash the GB bootloader over this one?
[Vibrant Android Development] adyscorpius:
Yup... Go ahead...
[Vibrant Android Development] dklimah:
Thanks Guys for the help! I just bricked my Vibrant. Got to use Odin for the first time. Went back to stock and uploaded Asgard with the OC kernel. Rainbow of death freaked me out! All fixed now!
[Vibrant Android Development] adyscorpius:
Lol... Well, you really gotta understand, bricking aint that easy.. Its a step more... UNRECOVERABLE... however, welcome back to life...

And yea, finally, did you use or not use the bootloaders? :-P
[Vibrant Android Development] dklimah:
Yes. I use the bootloaders. Was an easy fix. It took 30 seconds! I'm soooo glad. Since rooting my phone I've been dreading the day that this was going to happen. It was an easy fix, complicated but easy, none the less. It also deleted my sd card but whatever. I have a complete back up of it on my work PC.
[Vibrant Android Development] RoxAbout:
ok after reading the entire post....

What version of Odin do you use? recommend?

I have all the files, just need to know what version of Odin to grab / use.

on a side note...

since Ive installed biffmod rom the computer now says fails to find drivers...but it works over usb to access the int/ext mem cards...will that be a problem for Odin? or will it work cuz it will see the phone?

TIA
[Vibrant Android Development] dklimah:
You can find a link in xda for Odin. Search for it in the search tab. The newest is 1.3.X. here's the link for the drivers: http://xdaforums.com/showthread.php?t=728929

Hope that helps

Sent from by Vibrant using Tapatalk
[Vibrant Android Development] RoxAbout:
ok so much for reading all of the posts... im now stuck with the phone ! computer icons

History:

I was on biff mod/glitch and couldn't get into download mode....after reading on xda someone posted that in order to get back to download mode you had to get rid of glitch kernal via rom manager and install a ver of cm7 [i picked #100] I was able to get into d/l mode! and get Odin v1.70 to see the phone...

Ive tried up/pwr and dwn/pwr and all 3 nothing ,......!

EDIT I figured it out ..Read below

ok! bingo i pluged in the cable and then pressed both volume buttons and then put in the battery...and download mode popped up on the screen....

first thing I did was click/tick Re-Partion and select the 512.pit file and hit start [since thats what I read in the above posts]

Then I selected the pda_t959uvkb5.tar original kb5 rom and clicked start...

took about 2 mins and said pass!

pulled the battery pulled the cable put the battery back in and powered up!

booted up to android system recovery <3e> woohoo kb5!

hmm ok after my initial elation...

now im stuck in <3e> hell!!

e:cant mount /dev/block/st110

<invalid argument>

e:copy_dbdata_media:cant mount dbdata:

your storage not prepared yet. please use UI menu for formatand reboot action.

copy default media content failed.

ok at this point i used from the blue menu

delete all user data [passed ok]

delete cache data [passed ok]

reinstall packages ...gives this error

e:failed to open /mnt/internal_sd/update.zip (no such file or directory)

e:signature verification failed

installation aborted

ok lol went from dead phone to dead phone...

what to do now?

Thanks in advance!

GBBOOT-T959UVJFD.tar got my phone back to stock!

I used the above Battery out hold volume buttons in/down plug in usb cable and then put in the battery.... this gets download mode working [at least for me/my phone]

used odin3. v1.70 [andoid + slp] with the GBBOOT-T959UVJFD.tar rom and bingo im back to normal!

wow what fun
[Vibrant Android Development] adyscorpius:
It won't brick your phone... You can go ahead and flash them...

The phone will only brick if you have a lose USB connection and it fails during the ODIN flash, or your computer dies out in the middle or the process is disturbed in any possible way... Else, its safe...
[Vibrant Android Development] AngryDinosaur:
the only thing missing for GB now is GPS
[Vibrant Android Development] bbm21:
oh boy..... dont thinks its worth the risk haha i can live with the i9k splash screen
[Vibrant Android Development] adyscorpius:
Lol... Those issues could have happened even when you flashed the i9000 bootloaders...

BTW, where did you get a i9000 splash screen... The GB bootloader here shows Vibrant only...
[Vibrant Android Development] a1cshowoff:
Confirmed working with SimplyHoney... No rainbows at all.

Flashed from stock 2.1, bootloaded, then flashed honey. Thanks added!
[Vibrant Android Development] bbm21:
Ya I flashed the ones on the i9k thread like right after they came out and they fixed the rainbow and recovery problems that was a long time ago and I didn't know that it had the potential to brick my phone
[Vibrant Android Development] d3xt3rlab:
Worked great man thanks....no more Rainbows!! yay!!!
[Vibrant Android Development] adyscorpius:
If you know how to ODIN to stock ROMs, its going to be easy to flash these bootloaders... Follow the steps in the OP and flash the GB Bootloaders to get rid if the i9000 splash screen you get.
[Vibrant Android Development] bobshute:
I have often odined back to 2.1 JFD stock to clear up things going between 2.2, 2.2.1 and 2.3 roms.

Are the GB bootloaders compatible with 2.1?

If so there will never be a need to revert back to older bootloaders.

(I so wish the vibrant used das u-boot.bin like my nook does)
[Vibrant Android Development] adyscorpius:
Yes, it will work with 2.1 too... However, be very careful of not flashing any ROM or ODIN package containing an Sbl.bin or boot.bin only. They need to be flashed/upgraded/downgraded together and everything works fine...
[Vibrant Android Development] bobshute:
My JFD.tar does not have boot.bin or sbl.bin in it but it does have param.lfs.

Should I remove the param.lfs file from the JFD.tar?
[Vibrant Android Development] adyscorpius:
You should be good to go. No issues. However, if you do lose the splash screen and it goes to I9000, just reODIN the Gingerbread Bootloaders and you shall have your splash screen back.

EDIT: Give me 5 minutes, and I'll confirm to you.
[Vibrant Android Development] adyscorpius:
EDIT2: Ok! On ODINing to JFD, as I expected, the screen changed back to I9000. You may ODIN the Gingerbread bootloader file again to revert back to the Vibrant boot image. The bootloaders however are still the I9000 ones.
[Vibrant Android Development] Nabeel10:
So why would people want to flash a bootloader?
[Vibrant Android Development] adyscorpius:
Please read the first two posts for all such Information.
[Vibrant Android Development] hitman818:
Can I just ask how will it cm7 or miui, if it doesnt have rainbow issues?
[Vibrant Android Development] adyscorpius:
Umm, if I understand correctly what you just asked, it'll work perfectly on MIUI and CM7... No issues whatsoever...
[Vibrant Android Development] cashyftw:
I think it's because cm7 is build off different sources. I'm going to flash a gb rom from the captivate, and use our bootloaders.

Sent from my SGH-T959
[Vibrant Android Development] hitman818:
I know it will perfectlt, but if thers no rainbow issyes, whats the benefit?
[Vibrant Android Development] adyscorpius:
If you're comfortable with the present bootloaders, there's no need to flash.

However the new key mapping for recovery and download are awesome.

Like from within CM7 or MIUI just keep volume up and power pressed for 10 seconds and enter download mode and vol down and power for recovery.

Much better than keeping 3 buttons pressed for recovery, and turning off phone and then entering download mode like in the present case...
[Vibrant Android Development] adyscorpius:
You made me read so much... :-P

Odin to stock again. Then use any of the rooted kernel's .tar file and ODIN that, it'll get you the Clockwork recovery.

Try supercurio's voodoo kernels if you want or any other of your choice. You should have a rooted working phone...
[Vibrant Android Development] flapane:
How do I know which bootloader do I have, Froyo one or GB one on my CM7.1?
[Vibrant Android Development] Ashyford:
Once Running Custom GB BL and a GB ROM, How do I get to MIUI?

Hey Scorp, last month, from the stock froyo, I installed the custom GB bootloaders and flashed Simply Honey on a friend's phone (Vibrant T959). Flawless victory.

Now I want to move to MIUI. Through June and July, GB BL was not supported on MIUI. On pages 35 and 36 of this thread, it was stated that CM7/MIUI could handle GB BL.

My question: Is it ok to Flash MIUI or are there still issues with the custom GB Bootloaders and MIUI (e.g. unseen sd card)? If there are no problems, is the process to install MIUI to flash to JFD, root (if necessary), keep these GB bootloaders, and flash to MIUI, or can I wipe data, cache, and dalvik and flash?

Thanks.
[Vibrant Android Development] n64_ali:
Troubleshooting - bootloader related?

Hello all,

I understand that this isn't the Q/A section but because of the nature of the problem, I thought this would be a good place to troubleshoot. I had installed the GB Bootloader and Simple Honey 4.0 a while back. I then wanted to return to stock and flashed the official 2.1 rom through ODIN. Everything worked fine and phone booted normally. However, when I went to update the phone to Froyo through Kies Mini, it completed successfully but never rebooted. It is now completely bricked with nothing on the display, and no way to get it into download mode.

My question is: when I flashed back to stock, did that flash the original bootloader as well? What happened when I tried to flash it to Froyo that might have screwed it up? Was there any remnant of the GB bootloader left that might have jeopardized the process? And most importantly, is there anyway to recover from this short of JTAG/RIFF?

Thanks all.
[Vibrant Android Development] adyscorpius:
If I understand what you did correctly, It is..:

1. Flashed GB Bootloaders + GB ROM

2. ODINed to Stock 2.1 ROM (Still GB Bootloaders)

3. Upgraded to Froyo through Kies (Changed Boot.bin to Froyo but not Sbl.bin which is still GB)

4. Dead Phone!

Correct method would have been,

After or before Step 2, Flash Froyo Bootloaders (Original Vibrant stuff)

The best option is try a USB jig, else, nothing apart from a JTAG Riff box !!
[Vibrant Android Development] n64_ali:
Hey,

Thanks for the quick and informative reply. Just to follow up while I have a knowledgeable person's attention (and to prevent this from happening again), why was the phone able to successfully boot into the stock 2.1 rom with the GB bootloaders? It seems like if something was to go wrong, it should have happened then, no?

Hopefully someone can benefit from my mistake and not have the same thing happen to them. Thanks again for your help.
[Vibrant Android Development] caldran:
i think i bricked my phone help !!!!!

I was on froyo and bionix v2 with bali 1.8.8 kernel .. I thought of trying CM7 so started with the boot loader ..I did nt load the pit file as mentioned in the post. The ODIN displayed it as FAIL because it didnt find the pit file. now all I see is weird symbol saying phone is not connected to PC

Thanks you..but I had to read a lot for this .. :D
[Vibrant Android Development] cwalker0906:
Turn phone off....hold volume down button and plug in usb from pc....you should now boot in download mode...odin to stock
[Vibrant Android Development] parusia:
That phone computer screen is another screen for download mode. Just try to Odin the bootloaders again with the pit file and you will be set.
[Vibrant Android Development] derride8:
I'm on froyo rom, if I want to flash a gingerbread rom, all I have to do is odin back to 2.1 , then flash the gingerbread loader & then flash the ginger rom I choose. Is this right?

Thanks in advances...
[Vibrant Android Development] parusia:
I flashed the gingerbread bootloaders when I was on Froyo, and then I flash SH 3.8 and I have no problems, but that was long time ago. You do not going to have any problems going directly from Froyo to GB roms, with the GB bootloaders.
[Vibrant Android Development] gtoman7777777:
does switch your home and back buttons? because mine are switched for some reason when using Hawkish 4.1. any ideas why?