Database Info

[Stock Flash][Odin]EB13 Extended CW2.5+RFS or CW3+ext4 2/24/2011 inc. Root+Redir.

** Just got your epic and wanna dive in?
** Wanna clean upgrade?
** Wanna just check it out?
** Want stock Froyo EB13 AND root AND Clockwork all from a single Odin flash?
THIS IS NOT A CUSTOM ROM, IT IS SPRINT STOCK ROM. ALL SPRINT STOCK APPS ARE INCLUDED ( LIKE ITS A NEW PHONE) IT IS NOT MEANT FOR PEOPLE WITH CLOCKWORK ENABLED PHONES AND SHOULD ONLY BE USED IF YOU WISH TO RETURN TO A STOCK ROM OR IF YOUR PHONE DOESN'T BOOT.
Here ya go!
Thanks to:
- noobnl and Firon for the CW zImage from the 1click.
- noobnl for odin, CW redirector.
- skeeterslint,firon and bubby323 for the chats about it.
- Shabbypenguin for the DK17 system dump.
- bubby323 for the DK28 Tarball
- the mystery person who leaked DK17 Full.
- k0nane for the flashable dk17/DK28
- Kousch for CW
- Samsung(oddly) for bucking sprint and putting out the tarball ahead of time.
- Dameon87 for CW 3.0.0.5(ext4) and his deodexed eb13 and voicesearch fix
A Jump start for new users:
EB13 Kernel
EB13 Modem
EB13 Filesystem
Latest Clockwork installed as 3button Recovery AND quickboot/rom manager recovery bootable.
**Updates
02.24.11
- EB13 Stock system
- Pre Rooted
- Voice search Fix for ext4 deodexed. Get it here THANKS DAMEON!
12.05.10
- New OTA REL Release of DK28
- Two versions ODEX and DEODEX
- Clockwork Recovery and Recovery Re-director
- Rooted
- GPS "hacks" in place to help speed up locks.
11.27.10
- It is now zip aligned, pre-rooted, deodexed.
11.28.10
- Added in noobs redirector which works properly now.
- Added in the Market Fix (thanks Shabby!)
- Added in the no 100% battery popup.(thanks Daemon87 and raiderep!)
**FLASH AT OWN RISK**
WHEN YOU SELECT THE PIT OR TAR FILE IN THE PDA/PIT SECTIONS OF ODIN MAKE SURE THEY HAVE CHECKMARKS NEXT TO THEM IF THEY DONT TICK THE BOX. nOT RESPONSIBLE IN ANYWAY FOR ANYTHING THAT GOES WRONG, IF YOU'RE UNSURE ABOUT SOMETHING GO LOOK IT UP
It has been tested on my phone but it WILL overwrite everything(except SDcard of course so make a Nand)
Stock EB13 with Clockwork 2.5 and RFS
Instructions:
Step 1. Boot your phone into download by powering off your phone holding 1 on the keyboard and holding power til you see the little Yellow digger.
Step 2. On your computer launch the included odin.exe and select the included victory pit and under PDA select the included EB13-Extended-2.5.tar or EB13-Extended-3.tar
Step 3. Plug in the usb cable.(if it's done right you should see a yellow Com device.)
Step 4. Click Start and wait.
Stock EB13 Deodexed EXT4 + CW 3.0.0.6
Instructions:
Step 1. Boot your phone into download by powering off your phone holding 1 on the keyboard and holding power til you see the little Yellow digger.
Step 2. On your computer launch the included odin.exe and select the included EB13-ext4.pit and under PDA select the included EB13-Extended-3.tar
Step 3. Plug in the usb cable.(if it's done right you should see a yellow Com device.)
Step 4. Tick Repartition
Step 4. Click Start and wait.
That's it. You've got EB13 Release and clockwork preinstalled, rooted, and ready to use.To get into Clockwork, hold Volume Down Camera and Power to flash your own rom.
Enjoy!.
Extras
Legacy Items only:
Download for DK28: SPH-D700-DK28-Extended (ODEX Version)
Dowload for DK28: SPH-D700-DK28-Extended-D (Deodexed Version) **UPDATED
Download for DK17: SPH-D700-DK17-Extended
** Recovery can be accessed via adb reboot recovery, quickboot AND Rom Manager.
** ADB and unsigned zips turned off by default.
[/COLOR]

art3mis-nyc said:
** Just got your epic and wanna dive in?
** Wanna clean upgrade?
** Wanna just check it out?
** Want stock Froyo DK17 AND root AND Clockwork all from a single Odin flash?
Here ya go!
Thanks to:
- noobnl and Firon for the CW zImage from the 1click
- noobnl for odin
- skeeterslint,firon and bubby323 for the chats about it.
- Shabbypinguin for the system dump
- the mystery person who leaked DK17 Full.
- k0nane for the flashable dk17
A Jump start for new users:
DK17 Kernel
DK17 Modem
DK17 Filesystem
Latest Clockwork installed as 3button Recovery.
It is now zip aligned, pre-rooted, deodexed.
**FLASH AT OWN RISK**
It has been tested on my phone but it WILL overwrite everything(except SDcard of course so make a Nand)
Notable Fixes from the dk17 kernel are that the camera doesn't FC, lock-screen lag is gone and that Barcode Reader will work again!
Download: SPH-D700-DK17-Extended
Step 1. Boot your phone into download by powering off your phone holding 1 on the keyboard and holding power til you see the little Yellow digger.
Step 2. On your computer launch odin.exe and select the victory pit and under PDA select the SPH-D700-DK17-Extended.tar
Step 3. Plug in the usb cable.(if it's done right you should see a yellow Com device.)
Step 4. Click Start and wait.
That's it. You've got DK17 Release and clockwork preinstalled, rooted, zipaligned, deodexed and ready to use.To get into Clockwork, hold Volume Down Camera and Power to flash your own rom.
Enjoy!.
Click to expand...
Click to collapse
I was the tester and its working great

who is shabbypinguin?

shabbypenguin said:
who is shabbypinguin?
Click to expand...
Click to collapse
one to many penguins thats who!

Does gps work with version? Can't get gps to work with any dk17 rom
Sent from my SPH-D700 using Tapatalk

TheBurgh said:
Does gps work with version? Can't get gps to work with any dk17 rom
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I'm gonna say that it falls into the category of "works for me"
just go outside when you first launch maps(navigation/the gps button)

A good day

art3mis-nyc said:
I'm gonna say that it falls into the category of "works for me"
just go outside when you first launch maps(navigation/the gps button)
Click to expand...
Click to collapse
Wipe data and all caches before running odin. I already have dk17 on the phone
Sent from my SPH-D700 using Tapatalk

I would like top know if this wil make gps at least work without ising di18
Sent from my SPH-D700 using Tapatalk

adamw1101 said:
I would like top know if this wil make gps at least work without ising di18
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Instead of asking why not try, you're on a developer board, that more or elss means you're willing to mess with stuff to see if it works.
As i've said it works for me, your mileage may very so give it a shot and for gods sake READ THE FIRST POST as odin will wipe your phone(no sd just phone)

Thanks. This is a nice convenient time saver. Hopefully there will be one of these when the official froyo is released.
Sent from my SPH-D700 using Tapatalk

Cool stuff. Thanks for the nod.
Sent from my Epic

art3mis-nyc said:
Instead of asking why not try, you're on a developer board, that more or elss means you're willing to mess with stuff to see if it works.
As i've said it works for me, your mileage may very so give it a shot and for gods sake READ THE FIRST POST as odin will wipe your phone(no sd just phone)
Click to expand...
Click to collapse
geez sorry
Sent from my SPH-D700 using Tapatalk

thanks for this

Odin is hanging on boot.bin. I wish there was a way we could do all this via an update.zip, Odin is such a pain in the ass to work with.

gophergun said:
Odin is hanging on boot.bin. I wish there was a way we could do all this via an update.zip, Odin is such a pain in the ass to work with.
Click to expand...
Click to collapse
Always reboot pc before running odin and make sure you don't have pc studio running
Sent from my SPH-D700 using Tapatalk

Are we supposed to check Reboot and DebugEn? Or do we just leave it as is like the 1st post says? Because in the guide about using ODIN it says to check those
EDIT; My bad forgot that this is the new version of ODIN, so I guess we just follow the instructions

adamw1101 said:
Always reboot pc before running odin and make sure you don't have pc studio running
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Done, still having the same issue. I've never heard of PC Studio before looking it up now, so I presume it's not running, unless it's installed with the drivers or something. In any case, I'm gonna try uninstalling MSE and see if that makes a difference, but I've been screwing around with Odin and this half-bricked phone for two days now, so I don't have high hopes.

gophergun said:
Done, still having the same issue. I've never heard of PC Studio before looking it up now, so I presume it's not running, unless it's installed with the drivers or something. In any case, I'm gonna try uninstalling MSE and see if that makes a difference, but I've been screwing around with Odin and this half-bricked phone for two days now, so I don't have high hopes.
Click to expand...
Click to collapse
for odin 1.61(with the victory .pit) only check timereset and reboot
NOTHING else. with this rom.
make sure that you start odin first before connecting the usb(just to be sure)
and if you have issues, make sure that the usb is capable of the proper power, ie not through a hub, and disconnect non essential usb things.(mouse and keyboard are obviously essential)
if that fails try removeing the drivers fully, and reinstlal them with the phone plugged into a different port.

If you already have DK17 installed, can you wipe data and all caches and start from scratch. I can't get gps to work with DK17 or any rom
Sent from my SPH-D700 using Tapatalk

What exactly bricks a Captivate?

Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App

rufex2001 said:
Hi, I've had the glorious captivate for a few weeks now and I constantly read this forum. I am now ready to flash my phone and while I am not really afraid to do it, since I used to flash my Nokia 5800 every week, I wonder what is it during the process of flashing and loading a new rom that can cause the phone to get bricked? Are some parts riskier than others? Is there some common mistake or error or something people usually forget that kills it?
I'd appreciate some answers, since I love my phone and would hate to brick it.
Thank you very much! XDA rules!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you test the phone to make sure it can accept the button combinations to go into download mode (almost all do, except for a batch of faulty ones), there is almost nothing you can do that will truly "brick" the phone. A bad or interrupted flash will result in a boot loop, which you can recover from by forcing download mode, and using Odin to reflash back to stock.

Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.

Basically what causes a brick in any electronic equipment is from an interruption/error in any boot critical files. The item does not have the proper/complete instruction to turn on. You could say it is like starting a car being told to first put the key in
Sent from my SAMSUNG-SGH-I897 using XDA App

If you can use the 3 button combos to get into download or recovery mode, you are good to go. The only danger would be a bad Odin flash, but even so you'll have a chance to recover it by making a cheap USB jig (3 100k Ohm resistors into pins 3 and 4, I think, of the usb port) or buying one. This will boot the phone straight into Download mode.
When using Odin, there is only one stage where you can brick your phone for good, during the bootloader copy process, which probably takes less than a second.

Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App

rufex2001 said:
Thanks for the replies! I just tried it and I got the 3 button into download mode combo, so that's great! Now, what other options do I have for flashing besides Odin? Apparently Odin is not the safest, huh? And is there a way to make the bootloader writing stage less risky?
Also, my Captivate is a 1007 build. Is that a good thing or a bad thing?
Thanks, again!
Sent from my Samsung Captivate using the XDA App
Click to expand...
Click to collapse
My Cappy is a 1007 build, too. I've soft bricked my phone more times than I can count, but Odin hasn't had anything to do with it. It can do it, though.
At one time in my life I flashed a new ROM every day, and I used Odin every time before I flashed.
On a side note, back when I flashed my first ROM, I pulled the battery during the first boot, dropped it, and then flashed another ROM without using Odin, and it never bricked it, so that should give you a good idea of how hard it is to brick these phones. Lol

Stupidity.
Sent from my Captivate.

opcow said:
Flashing the first and second bootloaders would be the most dangerous, which is why the Odin one-click flasher is so bad. Also, the USB connection is a prime source of failure which is another reason to avoid Odin. So, if you have working button combos you are pretty unlikely to brick the phone as long as you avoid unnecessarily using any version of Odin.
Note: DesignGears includes sbl.bin (the second bootloader) in his ROMs, but since you aren't flashing it via USB it's relatively safe and it does have the side-effect of fixing you button combos if they aren't working. On the other hand, if you aren't using the one-click then you probably already have a good sbl.bin and so it's not needed.
Click to expand...
Click to collapse
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?

No odin really is not that bad just don't unplug it while it is running. You would not want to unplug your computer when flashing a new bios
Sent from my SAMSUNG-SGH-I897 using XDA App

Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Sorry for any dumb or repeated question I may be asking.
Sent from my SAMSUNG-SGH-I897 using XDA App

Pierce533 said:
I didn't realize Odin one click was so bad. I have been using Odin3 one click routinely now for a couple weeks as I flash back and forth trying out all these great ROMs to see what I like and so far (knock on wood I guess?) I haven't had any problems at all.
So, now that I have used Odin one click many times over, does my Cappy now have a bad sbl.bin?
Click to expand...
Click to collapse
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.

rufex2001 said:
Right, so if not Odin, what can I use for flashing? Can I do it all with the sdk using adb?
Also, I've been going through the guides and other stickies and apparently Odin is necessary only to flash back to stock. For rooting and installing new roms only the update.zip file and clockwork recovery are necessary. Could you do the same procedure to flash back to stock?
Click to expand...
Click to collapse
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.

opcow said:
Odin isn't bad so much as an unnecessary risk. There are a lot of potential causes of failure: user error, accidents, flakey USB ports or software from other vendors that interferes with your drivers. The there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build. I can safely odin flash all day if I need to, but there's just no reason to. And if you look around these forums you will see a lot of people crying after an odin mishap.
Click to expand...
Click to collapse
Thanks for the info. Is there a stock I897UCJF6 ROM that can be flashed with CWM? I haven't been able to find one and if there is one I would like to have one around to use. Thanks for taking the time to answer my questions.

opcow said:
I keep a CWM update.zip on my sdcard for reinstalling CWM and I flash my ROMs with CWM. I also keep a couple of spare know good ROM zips on the sdcard to go back to in case something goes wrong with a new install.
Click to expand...
Click to collapse
That is exactly the sort of thing I had in mind! So I guess I could keep a CWM update.zip and a stock rom update.zip and some custom roms and just do everything directly from the phone and without Odin, right? Or am I missing something?
Sent from my SAMSUNG-SGH-I897 using XDA App

Guns don't kill people

opcow said:
Odin isn't bad so much as an unnecessary risk. Then there the fact that people use the one-click and lose their button combos or brick their phone by using the one-click on a 1010+ build.
Click to expand...
Click to collapse
Yep. I have build 1008 that has always had the 3-button combo and lost it after using ODIN 1-click (I restored the combo with a later flash).
I believe opcow and others when they say that flashing back to stock is unnecessary. I just don't understand why the authors of some of these ROMs leave this as part of their installation guide.
Sent using XDA App

Pay close attention to the options in recovery when you are using a custom rom. It's part of the custom kernal, and of used properly can help you avoid odin. I avoid it because I have a mac and odin won't run on anything but windows. Custom recovery will allow you to format every part of the OS but the sbl.bin. Also in some custom recoveries there is an option to mount usb. This will allow you to format the internal sd then copy a new rom.zip and flash if you really want a clean flash. If your doing this make sure you are able to mount your sd before you format anything. Avoid stock 2.2 kernals because they have 3e recovery. There are ways around that but they have to be in play before you end up in a bootloop.
3e recovery + bootloop= odin recovery "only option".
Make sure lag fix for rom kernal A understands lag fix for rom kernal B. Also usually only a concern for stock 2.2 kernal. Other than that really hard to brick this phone.
Sent from my SAMSUNG-SGH-I897 using XDA App

As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.

ryude said:
As long as you keep a CWM update.zip and a ROM on your internel sdcard at all times, I see no reason why you would ever have to use odin 1-click.
I get bootloops all the time, just pull the battery and then use vol up + vol down + pow to enter recovery to flash the ROM back. Make sure it's a wipe ROM.
If it's not a soft-brick, then you will need odin.
Click to expand...
Click to collapse
Could you please explain what a wipe ROM is? Thanks

flashing back & forth between gb & froyo

i just wanted this all in one place.i wanted my daily driver to be torch or fusion cause of call quality but also want to play around on gb roms.i found a safe way to go back and forth.if something happens to your phone i'm not responsible this is what works for me.
1.flash gb stock just like it says here:http://forum.xda-developers.com/showthread.php?t=1045734
2.i wanted mosaic on to play around with so i flashed mosaic.now from mosaic( I have only tried mosaic so far) you can flash back to 2.2 or 2.1 rom that has NO secondary bootloaders(this is very important).and you have to be on http://forum.xda-developers.com/showthread.php?t=1042543 the kernel from here in order for this to work cause it uses cwm 2.5 still.
3.make sure you wipe data/factory reset and also wipe cache partition and dalvik cache in between flashing roms.
4.if on talon kernel you cant flash from 2.3 to 2.2 cause it uses cwm 3.0.so you need to get kernel flasher from market and the this file http://etc.muteheadlight.net/android/I9000_reoriented_vG.1.1_novoo.tar and flash it from kernel flasher it will put you back on cwm 2.5 and you can go back to 2.2 from there.
this has worked for me several times today i wanted to make sure it worked go and thank all the devs on there respected paged.they work hard on all this development show some appreciation.
again dont mix boot loaders make sure the rom you are flashing does not flash boot loaders.just stay on gb boot loaders.as it is stated you will brick your phone mixing boot loaders.
I hope this helps some people out and explains it good enough.

I just use odin one click to flash back to stock then flash by froyo rom of choice.

To Gingerbread from 2.1 bootloaders:
odin flash bootloader and reorient kernel package HERE (7mb)
odin flash talon or other kernel with CWM3 built in
boot into CWM3
CWM3 flash GB wipe rom!
Back to Eclair/Froyo: (keeping GB booties)
Odin flash a Kernel with CWM2.5 built in (onix)
boot into CWM2
CWM2 flash 2.1 or 2.2 wipe rom.
------AVOID ROMS WITH SBL (secondary boot loader) LIKE A PLAGUE!!! or built-in 3 button fix!----- YOU WILL BRICK!!
****To not worry about mixing Bootloaders or the SBL on Eclair/Froyo roms flash odin-one-click to get stock booties before Odin flashing a Cwm2.5 kernel.
Easy Peasy Lemon Squeezy

i also use odin one-click to get back to stock

Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897

Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.

studacris said:
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
Click to expand...
Click to collapse
I'm on a mac I have a pc around but I swear if you saw it you'd be a little nervous to it's a cheap old lap top running xp it doesn't even have a battery, I'd be fine with odin if I had faith in my pc. That being said don't mention heimdall it doesn't recognize 2.1 bootloaders so in order to move up I still need odin.
Sent from my SAMSUNG-SGH-I897

heimdall doesnt recognize 2.1 bootloaders? really?
how was it created with 2.1 bootloaders before the 2.3 ones ever existed??
thats news to me.... learn somethin new every day...
*sarcasm*

This an interesting post from the guys that wrote heimdall the first is a list of confirmed devices that work with heimdall the eighth post is a list of confirmed working bootloaders and osx compatability i9000 this should give you an idea of what I'm talking about. Out of ten only two support osx. As far as the i897 is concerned if you ever flashed your phone with odin 1click and I have the boot loaders included do not support osx. THAT'D be a fact . *touchee*
Sent from my SAMSUNG-SGH-I897

Here's the linkhttp://forum.xda-developers.com/showthread.php?t=891518
Sent from my SAMSUNG-SGH-I897

1tontomato said:
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
no problems so far.just wipe everything and factory reset clear data in recovery the key there is to be in cwm2.5 and not 3.0. and to never flash anything with secondary bootloaders.

Hey if Im currently on a JVH ROM, and want to try out the Galaxy Sense i9000, but the whole deal about the bootloaders is a little irrating. And its even trickier for me to go back to stock considering I have a build 1010, thus One Click soft bricks my phone (*I have a jig*). But it really isnt a big deal because I use the JH2 method and iCezars method for flashing back without risk, without replacing the bootloaders. Those are the two methods I have had to flash back to stock while on a Gingerbread ROM.
But my question lies in whether I can flash back to stock using one of the two methods I stated above which DO NOT FLASH BOOTLOADERS and follow the instructions in the Sense i9000 thread (This isnt a how to, to flash, because from December--February all I did was flash MIUI and CM7), but rather do you know if I could flash with GB bootloaders or would it be too big of a mess?
And if I cant can someone point me into a direction of a .tar file that contains BOTH BOOTLOADERS such as Odin One Click but I have to use Odin 3 and manually put it in and flash.
Thanks!

Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.

studacris said:
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
Click to expand...
Click to collapse
Hmm.. I was seriously thinking that but I was worried that it would completely brick the phone because it does flash both bootloaders thus completely bricking the phone.
If I knew I could just Jig it back like ive had to do twice when I used Odin One Click Id use the JH2 package or Cezars and be good.
But since im playing with bootloaders Im worried that it will completely brick cause One Click doesnt even work on my phone.

it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders

studacris said:
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
Click to expand...
Click to collapse
yes I know that im not trying to argue you with you... hahah
Im just saying that I dont know Im just a little hesitant as I havent used Odin One Click in a while, plus the fact that it'll be twice the nerve racking coming from Gingerbread Bootloaders.
That is the one thing that is a little scary, but I know if anything flashes on to the screen im good to go, but just a little nervous, but am seriously considering just using the Odin One Click, and just praying that it at least flashes the AT&T screen then off like it normally does.
But I dont know if it'll work the same with GB, I know its mostly in my head but hahahaha
EDIT: I havent used One Click in a while should I wipe my phone before? And secondly I assume disabling lagfix?

FLASHED ONE CLICK.... Going now I will keep it posted when I get back to stock.
the bootloaders though flash went well so I think im in the clear. Lets hope : D
UPDATE: It soft bricked, Jig--> now on Stock.
THANKS SO MUCH!

No problem man.
TRUST THE ZOMBIE!!

Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?

Soccer_Dad said:
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Click to expand...
Click to collapse
please read post 3
i wrote it. i know its there..

bootloaders! aka fix the rainbow garbage on awesome rom leaks

ok i see since it has been so long since all the rogers development started people dont really remember about all the rainbow problems and how they were fixed and how the fix needs source code.
we now have bootloaders available in leaks from samsung. they are needed with the stock kernels that come in the leaks to avoid rainbow garbage. i am providing the bootloaders to be flashed in heimdall without having to flash a whole rom.
i would like to make this explicitly clear that if this bricks your phone i am not to blame. there is a significant risk when flashing bootloaders! though the infuse seems to have safety measures i strongly recommend only flashing once. and if your phone becomes a brick you will need to solder things to the phone to fix it via j-tag or adam outlers unbrickable mod. be cautious! dont flash boot.bin without sbl.bin, dont flash sbl.bin without boot.bin, dont mix up the partitions, and if the phone bricks i dont want to know about it unless you want to pay me to fix it!
heimdall package
http://www.multiupload.com/GXUTF4QCJX
odin package (untested)
http://www.multiupload.com.... REMOVED May be failing to flash. very dangerous situation...
bootloaders for heimdall to be added through the "flash" tab (unzip first! ibl/pbl-boot.bin, sbl-sbl.bin)
http://www.multiupload.com/NAIA23JZL1
good luck!

Thanks for posting this. Hopefully it will help out with leak questions that tend to get asked over and over again.
Sent from my SAMSUNG-SGH-I997

Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!

MattSoRaven said:
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
Click to expand...
Click to collapse
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.

If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium

bigbadwolf311 said:
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
yes. that's how I would do it. the PDA slot seems to be automatic as far as partition sorting. the phone slot is for modems but if a modem is included in a package for the PDA slot it flashes just fine. the bootloaders are in the PDA packages normally so that's how I would do it.
please report results because I don't run windows and did not test that package.

I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium

Dani897 said:
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
Click to expand...
Click to collapse
I've been using the UCKJ2 bootloaders since they came out with no issues.

Entropy512 said:
I've been using the UCKJ2 bootloaders since they came out with no issues.
Click to expand...
Click to collapse
Same here.
Sent from my SAMSUNG-SGH-I997 using xda premium

bigbadwolf311 said:
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?

schmidtty661 said:
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
Click to expand...
Click to collapse
don't select repartition, no need for a pit, the rom shouldn't matter, the file should go in the PDA slot. remember I haven't tested it in Odin. I don't run windows and have little interest in using Odin for anything. phone needs to be in download mode just like flahong a rom. it should only take a second or two to flash. good luck

Cool i should be able to figure this out. Thanks for the quick response.

It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?

schmidtty661 said:
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
Click to expand...
Click to collapse
I have a bunch of downloads but nobody reported anything at all till now.
ill pull the Odin version for now. try it in heimdall. its not any harder to use.

Can you post an odin package.

I had an Odin package. I got a few downloads, didn't get any people thanking for it, didn't get any positive feedback that it worked and had one user report problems, see the last couple posts. I pulled the file for lack of evidence that it worked. I don't run windows and prefer heimdall so I haven't tested it in Odin. sorry but I suggest you either flash an entire rom leak then flash a non secure kernel through Odin ( any custom kernel should do also flashing back to stock should also do just fine) and then flash a rom or learn heimdall which works on windows as well as Mac and Linux. I would have done a oneclick package but it still requires the installation of the heimdall back end and I figured it was really no harder to just use the heimdall package system.

any chance of relink thats not at multiupload?
edit: disregard, found a workaround. might be useful in future tho.

[Q] Infuse 4g - Broken CWM - ICS 4.0.4 Infinitum Rom

Hello, I am a long-time viewer of xda but a new member, this is my first post.
(and yes, i looked for a similar theard. i could not find one.)
So, onto the problem.
I flashed Infinitum 1.1.1 to my Infuse using cwm recovery. I noticed problems right off the bat when after i had installed the zip, i rebooted into recovery then it got stuck on the samsung logo and i had to pull the battery (a normal event when flashing this rom) So when i pulled the battery and booted into recovery to try again, the cwm recovery was terribly screwed up. The top half of the screen was pixelated, and the navigation menu was off center. I was still able to use cwm to flash the rom successfully, But cwm remains srewed up.
So i tried to reflash cwm recovery using rom manager. but when i rebooted i was stuck in a recovery boot-loop that i had to get out of using odin.
I then flashed the rom again using the same procedure suggested by its developer, and it worked, but cwm is still acting as it was before. (the pixelated top half of the screen and the off center navigation menu. )
So can i get some help? i thought about removing cwm the using some other recovery. I also heard that cwm wont work on ics, but im unsure what it is.
Thanks in advance.

You don't have Gingerbread bootloaders. That's why recovery looks the way it does.
You need to Odin or Heimdall back to Gingerbread stock (I find Heimdall much easier for this) and then flash Entropy's DD kernel to get back into red recovery to flash Infinitum.
Posts 1 and 2 in this thread are what you need: http://forum.xda-developers.com/showthread.php?t=1524081

lukas_s said:
You don't have Gingerbread bootloaders. That's why recovery looks the way it does.
You need to Odin or Heimdall back to Gingerbread stock (I find Heimdall much easier for this) and then flash Entropy's DD kernel to get back into red recovery to flash Infinitum.
Posts 1 and 2 in this thread are what you need: http://forum.xda-developers.com/showthread.php?t=1524081
Click to expand...
Click to collapse
I i came from froyo, and is there a way to get the bootloaders without reverting to gingerbread stock?

Hard2thexcore said:
I i came from froyo, and is there a way to get the bootloaders without reverting to gingerbread stock?
Click to expand...
Click to collapse
Yeah, ICS recovery doesn't play nice with Froyo bootloaders.
AFAIK, there is no way to get Gingerbread bootloaders without reverting to stock. With Heimdall it's an incredibly simple, and quick process. I just had to do it myself a couple nights ago

lukas_s said:
Yeah, ICS recovery doesn't play nice with Froyo bootloaders.
AFAIK, there is no way to get Gingerbread bootloaders without reverting to stock. With Heimdall it's an incredibly simple, and quick process. I just had to do it myself a couple nights ago
Click to expand...
Click to collapse
Thank man, one more thing, will going back to gingerbread stock work if the only time i have ever used gingerbread was when i used the Zeus rom. The only other thing i have had besides zeus and this ics rom was froyo.

Hard2thexcore said:
Thank man, one more thing, will going back to gingerbread stock work if the only time i have ever used gingerbread was when i used the Zeus rom. The only other thing i have had besides zeus and this ics rom was froyo.
Click to expand...
Click to collapse
Yup, it'll work just fine
Just follow all the instructions for Heimdall to a T (there aren't many) and everything will be fine

Yeah...heimdal is the best way to get bootloaders...odin doesnt always do it and no custom rom includes them that i am aware of...
I had written detailed instructions for another person...ill try and find them and paste it here...
Also-dont use rom manager, that thing is known to cause bricks/bootloops so using it is asking for bad ju-ju lol
Sent from my SAMSUNG-SGH-I997 using XDA

mg2195 said:
Have you tried flashing boot loaders?
Here is how to do it...
1) Download uclb3 heimdal by qckster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your problems should be gone
Download mode instructions
1) pull battery
2) put battery back in
3) hold volume up + down
4) connect phone to PC with USB cable *don't let go of volume*
Just because you were on gingerbread previously does nit mean you have ginger bread boot loaders...I had ginger bread since the first leaks and did not have boot loaders until a month or two ago when I flashed them using those steps above...
Good luck!
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
There you go...follow those instructions and your cwm will be fixed!!!
Also just added it to my op of infinitum...
Sent from my SAMSUNG-SGH-I997 using XDA

Thank you for posting the guide. I literally just got done flashing GB bootloaders to my Infuse because of the rainbow Recovery when I'm on ICS. I used Odin though and used GB loader that a member posted in the AOKP Uniporn thread. I was scared but there really isn't anything to be afraid of. I tried using Heimdall but dang that was nerve racking because I was trying to use it on Mac and it wouldn't let me do the flash.

Jammol said:
Thank you for posting the guide. I literally just got done flashing GB bootloaders to my Infuse because of the rainbow Recovery when I'm on ICS. I used Odin though and used GB loader that a member posted in the AOKP Uniporn thread. I was scared but there really isn't anything to be afraid of. I tried using Heimdall but dang that was nerve racking because I was trying to use it on Mac and it wouldn't let me do the flash.
Click to expand...
Click to collapse
Good deal, glad you got it sorted out. And to clear up some confusion that is in this thread: you don't have to flash an entire Gingerbread rom to get the bootloaders. We all have our preferred ways of doing it, but you CAN flash just the bootloaders.
Here is both a Heimdall and an Odin way to get JUST the bootloaders. That's all that is necessary for someone who has rainbow distortion issues on an ICS or Gingerbread rom.:
See the third post (HERE) in Entropy512's Unofficial CM9 thread for instructions on how to flash just the bootloaders using the Heimdall command line. Or, see the answer to question 1.) in the FAQ of the rooted UCLB3 Odin thread which is HERE.
mg2195 said:
Yeah...heimdal is the best way to get bootloaders...odin doesnt always do it
Click to expand...
Click to collapse
Heimdall is one way to get the bootloaders, and here's how I did it.:
heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin
The second part of your statement isn't true. Odin doesn't do it only when the user can't figure out how to use Odin.

thank you everyone.
Being a creature of habit i ended up flashing to rom and bootloaders using odin. that did indeed fix CWM right up.

GB loader
Jammol said:
Thank you for posting the guide. I literally just got done flashing GB bootloaders to my Infuse because of the rainbow Recovery when I'm on ICS. I used Odin though and used GB loader that a member posted in the AOKP Uniporn thread. I was scared but there really isn't anything to be afraid of. I tried using Heimdall but dang that was nerve racking because I was trying to use it on Mac and it wouldn't let me do the flash.
Click to expand...
Click to collapse
I am trying to get those GB Bootloaders. Would you be able to provide them ? or to provide the AOKP Uniport thread ?

RemiChartier said:
I am trying to get those GB Bootloaders. Would you be able to provide them ? or to provide the AOKP Uniport thread ?
Click to expand...
Click to collapse
Unfortunately I haven't had this device for over 3 years now. You'll have to do some searching for that.

Jammol said:
Unfortunately I haven't had this device for over 3 years now. You'll have to do some searching for that.
Click to expand...
Click to collapse
Thanks, I have found the GG boot.bin and sbl.bin in another thread, I will update later on this thread.

RemiChartier said:
Thanks, I have found the GG boot.bin and sbl.bin in another thread, I will update later on this thread.
Click to expand...
Click to collapse
Where did you find them? Please share...