yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] adyscorpius:
How are you going about it???
[Vibrant Android Development] MS_Guru:
heimdall'ing the individual piece parts sends me into a recovery loop. Both the T959 and I9000 blank Param's. And I can't get the permissions right on an Odin image (Win Server 08 R2 x64). I'm assuming you build in a Linux environment?
[Vibrant Android Development] adyscorpius:
I use Cygwin bash shell on Windows to tar the file, and personally I wouldn't suggest using Heimdall, I've bricked my phone once because of it. Its been working perfectly on ODIN for almost everyone, including me. And I'm using a Windows environment, Windows 7 precisely....
[Vibrant Android Development] MS_Guru:
Don't think yur understanding... There's nothing wrong with the images you've built, or for that matter, the files in said images... I'm simply seeking a "Blank" param.lfs, with which I could "mount - push to phone - and be merry" with a "logo.jpg" of my choosing.

Examples....

Connexion2005's site with info and bootlogos

Original i9000 Thread by Connexion2005

Epic 4G Thread

Vibrant Thread

Blademonkey's bootlogos

Get me?
[Vibrant Android Development] raymasky:
i have flashed the GB bootloader and currently running a JVP based gingerbread rom. what is the process if i want to return to a froyo rom ? can i simply flash the rom and kernel through recovery ? Or do i have to odin to Stock froyo first ?
[Vibrant Android Development] adyscorpius:
If you wish to carry on with these bootloaders, you can flash any ROM/kernel without needing to change them... However be sure not to flash an ODIN package containing either one of sbl.bin or boot.bin alone...

If you want, you can flash the Froyo bootloaders back and you can revert to any froyo ROM with the default Vibrant bootloaders...
[Vibrant Android Development] justanothercrowd:
I would say since there is a larger risk flashing boot loaders that those that flashed GB's really have no reason to flash back to FROYO boot loaders until further notice....if ever. They are backward compatible and IMO have a nicer download/recovery key function.
[Vibrant Android Development] mattraab:
What format Is the boot image and resolution. I think I have a great idea that everyone would l love. Once I get that info I will post the image and we can see if people like it
[Vibrant Android Development] adyscorpius:
Its .jpg, size less than 70kb at max (original is around 60kb) and resolution is 480x800
[Vibrant Android Development] M_T_M:
Hello mates....cleaned up thread. Keep it civil and friendly, please.

Cheers,

M_T_M
[Vibrant Android Development] Dan_Brutal:
+1 The key combos are great.
[Vibrant Android Development] lucky 69:
Justanothercrowd @ +1 hi Jack good to see ya on here. Always loved your work. Very good advice for all
[Vibrant Android Development] طوني تبولة:
Now that I have installed this bootloader (custom GB), what do I need to do If I want to revert back to a Froyo ROM (the one in my Sig.) ? What If I want to install OverStock Kernel afterwards?

I currently, have Simply Honey 3.8 (Gingerbread)
[Vibrant Android Development] xlastshotx:
Can someone please help me this, I can not figure out why I cant flash this bootloader. I just get this error in Odin every time:

I have tried flashing the GB bootloader 5 times now and have tried all 4 of the bootloaders linked in the op. I have tried flashing the bootloader when running the T959UVJFD rom and the JVH_NO_BOOTLOADERS_PDA rom. Each time resulting in the image above. I have followed the directions exactly (confirming it with the video in the op). So I don't know what I am doing wrong :(
[Vibrant Android Development] laylovj:
Thanks a bunch dude...'twas a scary 10 seconds. :p

Is flashing back to stock froyo bootloader just as risky as flashing a GB bootloader?
[Vibrant Android Development] طوني تبولة:
Did you check the file MD5? I would guess it is a corrupted file
[Vibrant Android Development] xlastshotx:
Yeah, I checked the MD5 and it matches. I have also re-downloaded it a couple times and the file seems to be fine.

**Edit**

Ok well I got it working, I was connecting to Odin wrong I guess. I did Download mode, then unplug phone, then load Odin, then plug in phone, then add files and start. Which resulted in an error, but I found when I did it this way: Download mod, DIDNT unplug phone, load Odin, then add files and start it worked.
[Vibrant Android Development] raykovitz:
Thanks... That was simpler than I thought it would be.:D
[Vibrant Android Development] amandadam:
Flash OverStock,boot into recovery(power button and lower volume key),factory reset,flash froyo rom.

No need to flash froyo bootloaders,gb boots are backwards compatible.
[Vibrant Android Development] tomasitoc:
adyscorpius,

Wow, great work, you re the man!

thank you

thank you

thank you
[Vibrant Android Development] joe.kerwin:
I'm trying to odin to JFD and its giving me trouble for the first time. Is this bootloader related? Can't do anything w/ the phone but i do still have DL mode. I installed the GB bootloaders a few days ago.
[Vibrant Android Development] laylovj:
What do you mean you can't do anything?

PS: @ OP, any idea why you see the i9000 splash for a sec before the vibrant splash when you odin to jfd? Using the GB BL, btw.
[Vibrant Android Development] amandadam:
Did you flash CWM recovery for vibrant in Rom Manager?
[Vibrant Android Development] adyscorpius:
Sorry for the late replies... I'm travelling so only got Tapatalk and basic internet coverage at most places...

If you cant flash anything, try to use JFD, with a .pit file and repartition checked... that should logically solve it. Or do copy/paste the error you get...
[Vibrant Android Development] adyscorpius:
Yea, that cuz the ODIN package for JFD contains fresh splash screens and since it detects GB bootloaders from I9000 it shows them... If you guys want, I could up a JFD package that won't change the boot splash. Can do it by Monday late night...
[Vibrant Android Development] adyscorpius:
Recovery usually doesnt change the bootsplash... :)
[Vibrant Android Development] laylovj:
@ady

I would love this man. I'm a patient man. :)
[Vibrant Android Development] amandadam:
Thanks,I wasn't sure.When I restored a nan back up of a froyo rom,I flashed a new recovery,since the installed recovery was for i9000 for a ported gb rom.
[Vibrant Android Development] supraman89:
thank you, i was scared to even try it, i did it though, it worked :)
[Vibrant Android Development] laylovj:
Definitely man.
[Vibrant Android Development] Smartassassin:
***assistance needed***

i have solved my issue
[Vibrant Android Development] aaronhiep:
DO we have to untick F. Reset time? I saw it in the video but it doesn't say in the instructions?
[Vibrant Android Development] bobshute:
For those of you that want to change the boot splash screen connexion2005 in the captivate forum has put together a process and the files needed to do this.

They work on the Vibrant as well as the Captivate.

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

He has two versions one for eclair/froyo and one for gingerbread. I tested it using the GB bootloaders here (thank you adyscorpius) and it works great.

My new boot image to revist my past.

Newer is for the best team in baseball.
[Vibrant Android Development] lewishollow:
I apologize if this is a dumb question, but the files downloadable from the OP are all .tar.md5. do I just remove the .md5 from the file name?

Thanks!
[Vibrant Android Development] amandadam:
Flash as is.
[Vibrant Android Development] horatiob:
does this have the mute/unmute issue?
[Vibrant Android Development] laylovj:
Any news on this? No rush..just wondering if it's going to happen.

And...what would happen if I delete the param.lfs in the odin file?
[Vibrant Android Development] adyscorpius:
Hey, I just returned from my trip man... Dead tired after riding for almost 14 hours, with 5 in the rain...

Well yes, you basically need to delete the param.lfs from the ODIN package. I didn't want people spoiling their ODIN packages themselves, so was uploading something without param.lfs

But ya, if you know what you're doing, you just need to delete param.lfs and use the same ODIN package for JFD, and you'll have your bootloader image intact.
[Vibrant Android Development] z3NN9:
Does reflashing the boot loader fix this as well?
[Vibrant Android Development] adyscorpius:
Yes, it always does!

But ya, please do it in a fresh instance of ODIN.
[Vibrant Android Development] laylovj:
Ahh, well thanks again. I might just wait a day or to because I wanna be sure. :p
[Vibrant Android Development] laylovj:
Hmm...it flashed without the param..but for some reason...it wouldn't reboot all the way..just rebooted to recovery.

What if I use the param.lfs from the GB bootloader file and put it in the Odin file?

EDIT: It seems to work. :)

http://www.multiupload.com/HRYJKFLKFQ

MD5: 977E2136996E7138945447A8245D6776
[Vibrant Android Development] adyscorpius:
Great... I'll add this to the OP. Thanks for finding it out..!! I was sort of busy with my touring...
[Vibrant Android Development] jaikat:
hi guys,

i own a vibrant and a i9000, and i loved how the gingerbread bootloaders adyscorpius offered for the vibrant were backword compatible with froyo roms..

i went and looked in the i9000 section for something similar, and as i did find a thread that offered the bootloaders, they're saying they're not backword compatible.. meaning, if i want froyo i have to flash the froyo BL, and if gingerbread i have to flash the gingerbread BL..

i was wondering how backword compatibility is possible for the bootloaders offered here by adyscorpius for the vibrant, and they're not backword compatible for the i9000, even though the gingerbread bootloader came from the i9000 according to the OP

advice please !!

ps: i did ask in the i9000 section but no one answered :o
[Vibrant Android Development] adyscorpius:
Did you try flashing a Froyo rom after having Gingerbread Bootloaders on your phone? Also, try not to have a Param.lfs from a froyo base...

Just flash a CwM zip file of any Froyo ROM and see if that works for you... 99% it should... To keep this thread clear, I'd ask you to PM me.. We can sort it out there... I wouldn't want to confuse other people...
[Vibrant Android Development] strictlyrude27:
Heimdall segfaulted on me during the flash, and it resulted in a soft-bricked phone (picture of phone-!-computer). So don't use Heimdall.

That said, I can't get back into download mode. Tried the following methods:

hold down 3 buttons, pop battery in. Results in phone-!-computer

hold down volume up/down with battery in, pop in USB. Results in phone-!-computer

hold down all 3 buttons, pop in USB. Let phone-!-computer disappear, release power button. Results in phone-!-computer.

hold down volume up+power (a la OP keymapping), pop in USB. Results in phone-!-computer.

I'm now on a Windows machine with ODIN. Oddly, ODIN can see my phone go in and out, so I know this thing isn't dead. It's just a matter of getting into download mode.

My phone is not hardware locked.

I would appreciate anyone's help here. I don't have a download-mode jig.. I should probably get one?
[Vibrant Android Development] laylovj:
Dude jast flash back to stock and reflash..that's a download mode of sorts so just reflash.
[Vibrant Android Development] strictlyrude27:
I can't get into download mode or recovery mode. That's the point.
[Vibrant Android Development] laylovj:
Like I said, reflash. :) Odin should recognize your phone with that screen on so, yeah.
[Vibrant Android Development] strictlyrude27:
wow, what a tumultuous past couple hours it's been. thanks a lot for the help! phew :)

I wonder, was I in Download mode the entire time? Or was just coincidence that ODIN was able to see the phone?
[Vibrant Android Development] adyscorpius:
Well, the download mode image is stored in the factoryfs, so everytime you screw that partition, the image shifts to what is stored in the param.lfs, which is the phone ! Computer.

That's basically to tell you that something on the phone's screwed up.

However, if you remember what bootloader you are on, then you can simply use the designated keys to enter DOwnload Mode, which will show as the Phone!Computer view, let ODIN recognize your phone, and if it does, flash the JFD or whichever image you use the normal way, and it'll reboot normally...

A Brick is where even that screen does not come... A rare scenario, though highly probable with Heimdall.. Dunno why, but it just seems to be a very vulnerable software to use for bootloaders atleast...
[Vibrant Android Development] apokrikorian:
stock bootloader

where can i get the stock bootloader for vibrant or atleast remove the bootloader so it doesnt say gt-i9000 when it starts up just vibrant?
[Vibrant Android Development] adyscorpius:
Seriously, I'll answer your question, but did you read the OP?
[Vibrant Android Development] apokrikorian:
yeah, i dont see the original bootloader
[Vibrant Android Development] adyscorpius:
It cant be more crystal clear !!!
[Vibrant Android Development] apokrikorian:
alright thanks lol. i got a little confused since the odin file i have brings my phone to eclair, not froyo since i downloaded it a few months ago...
[Vibrant Android Development] adyscorpius:
Even this ODIN file takes you to Eclair !! That's JFD...

But the bootloaders need not change as they are backward compatible.

I've used Gingerbread bootloaders on Eclair, froyo, CM7, and Gingerbread and it works perfectly fine...

If you loose the Vibrant screen, simply reflash the GB bootloaders or the Froyo bootloaders and you'll have it back... !!!
[Vibrant Android Development] PabxH:
I downloaded and it is an md5 file. ?? :confused:
[Vibrant Android Development] bobshute:
Odin uses a .tar or .tar.md5.

the .md5 contains the md5 hash which Odin checks before it flashes so it doesn't flash a bad file.

Just use the md5 as is.
[Vibrant Android Development] lilg754367:
hellp

so when you flash that gbboot file it still does not bring you back to stock because you have to use vol down and power button to get into recovery mode instead of all three buttons? anyway to fix this
[Vibrant Android Development] laylovj:
The GBBOOT JFD file doesn't flash bootloaders...you have to flash the froyo bootloaders again...
[Vibrant Android Development] supraman89:
I keep forgetting that the download mode combos switch when i install bootloaders, I just gave myself another mini heart attack, thinking to myself "dammit dads gonna get pissed when he finds out i bricked it". Thankfully i didn't :)
[Vibrant Android Development] MilkPudding:
A fuss-free flash on Simply Honey

Thanks.
[Vibrant Android Development] Demiurgic:
Surprised no-one mentioned yet that heimdall command line was updated to 1.2 which adds the much needed no reboot option.
[Vibrant Android Development] RaverX3X:
not noob question any chance getting this to work on the t959v as the sammy firmware leak had the i9000 bootloader but had a severly disabled sbl and boot file which prevents any methood of getting into recovery mode what so ever download mode works...

Just was curious as to the possablility :P
[Vibrant Android Development] adyscorpius:
If you've had Vibrant bootloaders for T959 work for you, or I9000 bootloaders work for you, this might work for you too !!! But very seriously, I'm not suggesting anything... !!! Be sure of what you're doing before you do this, and yes, a wrong bootloader = a Brick Phone !!! (Can be revived only with a JTag Riff box)
[Vibrant Android Development] RaverX3X:
Ty ya i have had to Jtag before lol fun stuff ya i dont randomly flash stuff i was just curious as it seems when they leaked kf 1 for the t959v it was using the i9000 bootloaders to boot it JUst if we can get this to work we can finally get cwm support :P
[Vibrant Android Development] Andreal:
Quick question:

Can I switch to 2.2.1 rom from 2.3.4 (simply honey 3.9,with GB bootloaders flashed) via CWM or do I need to flash froyo bootloader first -> then with ODIN to stock -> then some rooted rom (or root, CWM) -> and finally 2.2.1?

And what is exactly "JFD ODIN File - For use after installing Gingerbread Bootloaders",

is it full stock JFD rom WITH GB bootloader included?
[Vibrant Android Development] zacharias.maladroit:
JACKPOT ! :eek:

so there's practically Gingerbread bootloaders for the SGS, Captivate and Vibrant

excellent ! :)

where are the devs to work on the SGS (samsung source) to CM7 kernel port ?

there's no reason anymore NOT to do it :cool:
[Vibrant Android Development] nateskates:
I'm stuck on this in Odin:

"<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> Enter CS for MD5..

<ID:0/003> Leave CS..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> Sbl.bin"

It looks like it has yet to flash anything, so I decided to turn off my phone and put it back in download mode. It's still stuck at the same after trying to flash the bootloader again, however. Any help?
[Vibrant Android Development] adyscorpius:
Have you used ODIN before for other things?

You need to be very careful with ODIN, lose USB wires, correct drivers, and actually being in Download Mode with ODIN.

Also, after every ODIN, you should restart the program and also reenter Download mode to really make it a successful flash each time...

Given all of that, try reflashing a complete JFD, with repartition checked and also selecting a .pit file... Flash the GB Bootloaders after that, after rebooting again into download mode and restarting ODIN. It should flash then...
[Vibrant Android Development] nateskates:
Right after the second try I decided to flash to JFD. I think I'l give it a third try.

EDIT: It worked! Thanks.
[Vibrant Android Development] vbenkovskyy:
GINGERBREAD BOOTLOADER

I Flashed it and now I can't see my extenal_SD card fix it please!
[Vibrant Android Development] zacharias.maladroit:
you're using cyanogenmod 7 or MIUI ?

GB bootloaders don't work with those (yet)

access to external SD won't work (at least it's the same with the SGS / GT-i9000)

battery runtime in return might be better

not sure if it's the same case ...
[Vibrant Android Development] vbenkovskyy:
I'm using MIUI Rom. Thanks for your answer.
[Vibrant Android Development] cmrn89:
AMAZING! installed bootloader and worked perfectly! thanks so much
[Vibrant Android Development] dcaples002:
Can I flash these bootloaders using Heimdall
[Vibrant Android Development] adyscorpius:
Yes... Extract the files, place them in the respective placeholders and flash...
[Vibrant Android Development] lbw321:
I flashed lidroid 2.8 with GB bootloader.Then I odin the froyo bootloader without the param.lfs file，and still no rainbows.So I don't know whether it's possible to just flashed the GBbootloader param.lfs file to avoid the rainbow?
[Vibrant Android Development] adyscorpius:
I'll need to test it... Will check and get back to you... Am now using a Galaxy S2, so will need to ask my brother to give me his phone(Vibrant)...

Or maybe if someone else could test it too, then we might just be over with needing to flash Gingerbread bootloaders at all...
[Vibrant Android Development] Demiurgic:
Might be safer to use the command line with no reboot
[Vibrant Android Development] chirantan.f:
so if i install GB bootloaders and install a GB rom such as simply honey, i wont see my external SD?
[Vibrant Android Development] geoffcorey:
The external SD issues is with CM7 based roms only, not the Samsung roms.
[Vibrant Android Development] albanianbrotha:
GPS will work with the GB bootloaders right?
[Vibrant Android Development] krarvind:
Tried this on my T959D ( telus fascinate) very similar to t959 ( t-mobile vibrant including the key combo for getting into download and recovery, home back search key etc). I lost the 3 button combo when i used a GB Rom for I9000 and was hoping i will get it back with this. Flashed fine but the suggested combo not working to get into download or recovery, keeps booting ( displays vibrant then GT I9000) up the phone normally. Any ideas?
[Vibrant Android Development] adyscorpius:
GPS works irrespective of the bootloaders...
[Vibrant Android Development] adyscorpius:
If you want the stock combo, flash Froyo bootloaders...

The combi for both GB and froyo bootloaders are mentioned in the OP... Work fine with T959... Please try them as mentioned in the OP and hopefully they should work for you... :)
[Vibrant Android Development] krarvind:
I don't want stock combo, hence i flashed the GB bootloader. After flashing, i did try the vol down + power for recovery and vol up + power for download. neither would work. GPS and everything works fine for me. Would love to have this button combo working, so far no luck. I do have my USB jig just in case but that doesn't let me into recovery. May be this won't work on t959D after all. only on t959 i guess.
[Vibrant Android Development] daohoa:
what is a GB bootloader ? and what r the benefits of using it? Im on MIUI right now. Should i flash GB bootloader ?
[Vibrant Android Development] geoffcorey:
Running gb bootloaders on anything CM7 based will make your external sdcard inaccessible. Don't worry yourself with them. It does nothing good for you.
[Vibrant Android Development] daohoa:
thanks for your explanation
[Vibrant Android Development] kryer12:
Was able to install the GB Bootloaders without issue and then installed Malice 4.1. I love having gingerbread on my vibrant and it wasnt hard.

Thanks adyiscorpus
[Vibrant Android Development] cmrn89:
alright, I'm currently using this GB bootloader for Simply honey 3.9.1 (which has worked great so thanks again), but I am considering switching to CM7 which requires a froyo/eclair bootloader. Can I just odin back to stock then odin the stock bootloader posted here normally? or is there something else I have to do in order to take off the GB bootloader?
[Vibrant Android Development] adyscorpius:
ODIN to stock first, flash bootloaders then...
[Vibrant Android Development] draigons:
Just this evening I had to go back to stock, warrenty exchange. I odined back but still had bootloader from gingerbread. I ended up having to Odin the froyo/eclair bootloader. The reason is that the hbo bootloader works for them as well. I do not know what I did wrong but odinjng back the eclair/froyo bootloader and then I lost the gt-i9000 boot screan... I do not know if this helps just click thanks. If I am wrong then happy cm7 to you!
[Vibrant Android Development] adyscorpius:
I would like you guys to read the stuff! If ODIN to JFD tar file had contained the froyo bootloaders, you would have returned to stock bootloaders.

However, that's not the case.

You still need to flash Froyo bootloaders if you wish to load a Froyo ROM or CM7/MIUI even if CM7/MIUI is based on 2.3.4 (Gingerbread)
[Vibrant Android Development] cmrn89:
I odin'd back to stock, then followed the instructions flashed the froyo bootloader unchecking all the tic marks except pda and what not used the right file , Odin said it passed then I long pressed the power for 10 seconds to let it reboot, now its stuck at the galaxy s GT-I9000 screen. suggestions?
[Vibrant Android Development] cmrn89:
alright I reflashed the bootloader and it was the same thing, I would get stuck at the GT-I9000 screen so I pulled the battery to get into DL mode but the difference this time from the first time I flashed it is that now I have to hold down both volume keys instead of just the top. So I odin'd to stock again and its back to normal but does that mean I am on the froyo bootloader now?
[Vibrant Android Development] jaikat:
hey adyscorpius

i only use linux, and heidmall is the way to go for me, which allows for picking every single file i want to flash..

i was wondering if i could flash the boot.bin and sbl.bin "without" param.lfs, which if i'm not mistaken is only the boot image..

thanks
[Vibrant Android Development] ameedi600:
Hi if anyone can answer me this question, I would be really thankful. What do the gb bootloaders do? Also would I need the gb bootloaders for miui or for simply honey.