Database Develop

[Q] Can't Flash Stock Rom + Terrible Battery Life

My Captivate is only about a week old. After getting it, I immediately rooted it and installed stock Froyo, but wasn't satisfied with the battery life or performance. So I installed Darky's 7.5 ROM (nowipe version using the 'wipe data + cache' option in CWM) along with the glitterball kernel and JL3 modem. Performance and stability were excellent, but battery life was abysmal, even with no apps running and the CPU capped between 100MHz and 800MHz using SetCPU (which is plenty fast on this ROM). I'm talking about 10-15% drain per hour while on standby, packet data, wifi, bluetooth, GPS, and sync all off.
I attempted to flash back to stock to try other ROM's, but Odin one-click simply bricked my phone to the point where I needed a hardware jig. After much work, I was able to flash Cognition using the regular Odin and then use CWM to restore my phone back to the Darky's ROM state with all my data and apps intact. Battery life is still terrible though. I've tried several methods to revert my phone to a stock kernel, including Odin one-click, Odin with 3-button fix, and regular Odin loading various stock ROM PDA and PIT files.
The furthest I was able to get was a phone with a working recovery menu that gave me 'Kernel Panic' right after the AT&T logo. Otherwise, the phone would be completely bricked (no button combinations) and I'd have to reset it using the jig. However, flashing a custom ROM that *doesn't* require reverting to stock first (Odin-flashable), or restoring a backup from CWM works just fine every time, no matter how badly I brick the phone. It's just stock ROM's and kernels that I can't get to boot or install properly.
I'm running out of ideas, because this battery drain is unacceptable and my ROM choices are severely limited. I did try flashing some ROM's over Darky's (JPY) without the revert-to-stock step, but I always get weird problems like missing phone, message and contacts apps.
I would really appreciate it if someone could help me out.

You need to get your odin issues worked out. They are abnormal. One I would try to delete the prism then re download. Two please list steps your are following to flag with odin, hopefully it is an ready oversight someone xan point out to you.
Sent from my SGH-I897 using XDA App

mcord11758 said:
You need to get your odin issues worked out. They are abnormal. One I would try to delete the prism then re download. Two please list steps your are following to flag with odin, hopefully it is an ready oversight someone xan point out to you.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I have re-downloaded both Odin and the files to flash multiple times, confirmed by the '(1)' tacked onto the filenames in my download folders. My procedure:
1. Extract Odin and PIT file (if flashing with a PIT).
2. Run Odin as Administrator, select PDA tar/md5 file (and PIT file if applicable). Untick 'Auto Reboot'.
3. Put phone into download mode using volume button combo (or hardware jig if Odin already bricked my phone).
4. Plug phone in. Phone recognized immediately by Windows and Odin.
5. Click start in Odin. Procedure always completes successfully.
6. Battery pull and unplug phone. Put battery back in and turn phone on. If flashing a stock ROM, phone either gets kernel panic, or is bricked and all button combos are disabled.
The files I used for stock flashing were found in the Odin one-click + master clear thread and the Odin one-click button combo fix thread (which uses a PIT and PDA file). I used Odin 3 v1.0 when flashing PDA files (had no problems flashing cognition ROM or non-stock kernels).
For the one-click versions, I followed the above procedure (minus the selection of PDA/PIT files). One-click always bricks, regular Odin will either brick or cause kernel panic when flashing a stock ROM or kernel, depending on PDA/PIT files and the previous state of the phone.

When you run odin one click, were do things appear to go wrong
Sent from my SGH-I897 using XDA App

mcord11758 said:
When you run odin one click, were do things appear to go wrong
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
There's no sign of anything going wrong until the phone auto-reboots (since you can't disable that in one-click). Upon rebooting, the phone just loops the AT&T logo, requiring a battery pull. Button combinations do not work and the battery charge icon (when the phone is off) freezes when the phone is plugged in.

GGXtreme said:
There's no sign of anything going wrong until the phone auto-reboots (since you can't disable that in one-click). Upon rebooting, the phone just loops the AT&T logo, requiring a battery pull. Button combinations do not work and the battery charge icon (when the phone is off) freezes when the phone is plugged in.
Click to expand...
Click to collapse
are you at&t our rogers? What us the name if the odin file you are using/
Sent from my SGH-I897 using XDA App

mcord11758 said:
are you at&t our rogers? What us the name if the odin file you are using/
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm on AT&T. Odin files I've tried include:
Odin3 v1.3.exe (bundled with Odin3.ini and s1_odin_20100803.pit)
Odin3_v1.0.exe (bundled with PIT.pit and used with PDA.tar)
Odin.exe (bundled with PIT.pit and PDA.tar for Cognition)
I897UCJF6-final-OCD-REV0.exe
All of the Odin executables (with the exception of the one-click) work fine flashing Cognition and I9000_reoriented_v2.3.0.tar (xcalib kernel), but not with the included PDA.tar files. When I say 'work fine', I mean flash the phone into a workable, non-bricked state, since Odin never throws me any errors or failures.

*bump*
Is this hopeless? I've asked about this elsewhere, and no one seems to have any suggestions. My phone has been up and running fine on multiple different custom ROM's and kernels, but it still bugs me that I can't flash back to stock if needed. Also, any suggestions on improving battery life are very welcome.

After searching around for a bit, it seems that Captivates from batches 1008 to 1010 cannot be flashed back to JF6 using any version of Odin. The closest that can be achieved is JH3 using Odin 1.7. This is pretty disappointing.
Oh well, I guess I have no luck with technology. Unless anyone feels like throwing battery life suggestions at me, this thread can be closed/deleted I guess.

The battery probably just needs calibrating.
There are.multiple threads in the forum on this and I would be happy to point.you to them, bit.I am on the phone app and its a little more.difficult to do so.
Sent from my GT-I9000 using XDA App

Search development thread for I897UCJH7 - OTA by designgears. Close enough to JF6.
Sent from a phone somewhere in the universe

http://forum.xda-developers.com/showthread.php?t=731989 <-- this is what I use to go back to stock before every re-flash. Never had an issue.
Build 1008 phone - hobbling along with random reboots etc.. and no buttons working.
I wouldn't suggest using anything else to flash back to stock. Then flash your new ROM as usual. You do NOT need to do a "stock" 2.2 froyo ROM first before installing any custom ROM.
The simple way to flash correctly to a new ROM
Use Odin 1 Click I897UCJF6 back to Stock.
Root your Phone (Or if you kept the Update.zip from CWM you can fore go all of this )
Download ROM Manager - update Busybox
Put the ROM you wish to use on your SDCard
Go into CWM and flash as normal following the dev/cooks instructions.

cappysw10 said:
Search development thread for I897UCJH7 - OTA by designgears. Close enough to JF6.
Sent from a phone somewhere in the universe
Click to expand...
Click to collapse
Thanks. I eventually figured out the JH2 to JH7 trick. It seems I can't properly flash any ROM below JH3 using any version of Odin.
avgjoegeek said:
http://forum.xda-developers.com/showthread.php?t=731989 <-- this is what I use to go back to stock before every re-flash. Never had an issue.
Build 1008 phone - hobbling along with random reboots etc.. and no buttons working.
I wouldn't suggest using anything else to flash back to stock. Then flash your new ROM as usual. You do NOT need to do a "stock" 2.2 froyo ROM first before installing any custom ROM.
The simple way to flash correctly to a new ROM
Use Odin 1 Click I897UCJF6 back to Stock.
Root your Phone (Or if you kept the Update.zip from CWM you can fore go all of this )
Download ROM Manager - update Busybox
Put the ROM you wish to use on your SDCard
Go into CWM and flash as normal following the dev/cooks instructions.
Click to expand...
Click to collapse
That is what I've always been trying. Attempting to flash anything below JH3 with any version of Odin (one-click or regular with PDA/PIT files) ALWAYS bricks my phone and requires a jig, 100% of the time, using any computer. Flashing a newer/custom ROM works fine.

GGXtreme said:
Thanks. I eventually figured out the JH2 to JH7 trick. It seems I can't properly flash any ROM below JH3 using any version of Odin.
That is what I've always been trying. Attempting to flash anything below JH3 with any version of Odin (one-click or regular with PDA/PIT files) ALWAYS bricks my phone and requires a jig, 100% of the time, using any computer. Flashing a newer/custom ROM works fine.
Click to expand...
Click to collapse
intriguing the somewhat random button combo issues on some newer builds of phone

newter55 said:
intriguing the somewhat random button combo issues on some newer builds of phone
Click to expand...
Click to collapse
I can't remember if it did, but I think the actual issue is that my phone came with JH7 (not JF6) and is actually incapable of running older firmware due to some difference in the hardware/build. That's why flashing stock JH7 seems to work fine.

[Q] Kernel flashing confusion with speedmod and Voodoo

Hi everyone, it's my first post here and I'm majorly confused.
What's going on? In a nutshell, I somehow can't fully flash the voodoo kernel.
Let me first describe my setup:
Samsung Galaxy S GT-I9000 with 2.2.1 FROYO.XWJS5 firmware.
For flashing I'm using Odin v1.7 running on a Sony Vaio Win 7 laptop and the Samsung supplied USB cable directly from the USB port, no hub or anything.
With that setup (unflashed kernel, no tweaks) my phone scored between 950 and 1050 points with Quadrant.
I am root
So what did I do?
After reading about the audio improvements that voodoo can make, I wanted to flash the Voodoo kernel from dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-unsigned-update.zip
When I enter recovery mode (up+home+power) all I get is the < 3e > recovery mode which doesn't have any other useful option than run update.zip. When I rename the kernel's zip file to update.zip it of course won't let me run it since it's unsigned.
So I used Odin with dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-odin-pda.tar
I put the phone in download mode (down+home+power), start Odin v1.7, add the .tar as PDA and the only(!) boxes checked are Auto Reboot and F. Reset Time.
I then connect the phone via USB, the box saying something like 0:COM9 turns yellow and I start the flashing.
It seems to flash and reboots, but I get no options and it obviously doesn't convert anything since the boot time is normal. Entering "mount | grep -i ext4" in the terminal doesn't return anything and the Quadrant score stays the same.
Booting into recovery gives the same old < 3e > recovery. BUT the settings->about tells me that I have 2.6.32.9 curio carton #Voodoo_stable_5.4.1 running. So I install the Voodoo Control App 0.8.4 and it seems to work since I can set force analog vol. key and set the analog output level with it.
But seemingly no lag fix. So I enter IRC project-voodoo and ask for help. Among others, phalanger takes care of me. After trying various methods (ROM Manager, Odin, SGS Kernel Flasher) I flashed the speedmod-kernel-k13c-500hz-CWM kernel (dl from xda) with Odin. This worked flawlessly, and I now can boot into CWM recovery.
Here it get's weird. I applied the lagfix (converted to ext4), which worked smoothly. Quadrant scored 1300 points, "mount | grep -i ext4" returned something and the system was snappier. Cool, I thought, let's see what happens if I now run the Voodoo .zip from the CWM recovery, which I did without reverting to rfs. It worked, but it reset my firmware.
So I again flash speedmod with Odin, revert to rfs (data, cache and dbdata are now rfs) and restore a backup from before the lagfix (all this in CWM recovery). The phone is back to "normal", I have all my apps and the speedmod kernel, but of course no ext4! And now Quadrant still scores around 1200 points, how is that possible? I now again used SGS Kernel Flasher to flash the Voodoo Kernel to give me the audio options, what seemingly works, but I'm very confused.
Why can't I run the Voodoo lagfix, why do I still have < 3e > recovery and why isn't the phone running faster?

Davestar2000 said:
Hi everyone, it's my first post here and I'm majorly confused.
What's going on? In a nutshell, I somehow can't fully flash the voodoo kernel.
Let me first describe my setup:
Samsung Galaxy S GT-I9000 with 2.2.1 FROYO.XWJS5 firmware.
For flashing I'm using Odin v1.7 running on a Sony Vaio Win 7 laptop and the Samsung supplied USB cable directly from the USB port, no hub or anything.
With that setup (unflashed kernel, no tweaks) my phone scored between 950 and 1050 points with Quadrant.
I am root
So what did I do?
After reading about the audio improvements that voodoo can make, I wanted to flash the Voodoo kernel from dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-unsigned-update.zip
When I enter recovery mode (up+home+power) all I get is the < 3e > recovery mode which doesn't have any other useful option than run update.zip. When I rename the kernel's zip file to update.zip it of course won't let me run it since it's unsigned.
So I used Odin with dl.project-voodoo.org/Voodoo-stable-5.4.1-Froyo-2.2.1-GT-I9000-odin-pda.tar
I put the phone in download mode (down+home+power), start Odin v1.7, add the .tar as PDA and the only(!) boxes checked are Auto Reboot and F. Reset Time.
I then connect the phone via USB, the box saying something like 0:COM9 turns yellow and I start the flashing.
It seems to flash and reboots, but I get no options and it obviously doesn't convert anything since the boot time is normal. Entering "mount | grep -i ext4" in the terminal doesn't return anything and the Quadrant score stays the same.
Booting into recovery gives the same old < 3e > recovery. BUT the settings->about tells me that I have 2.6.32.9 curio carton #Voodoo_stable_5.4.1 running. So I install the Voodoo Control App 0.8.4 and it seems to work since I can set force analog vol. key and set the analog output level with it.
But seemingly no lag fix. So I enter IRC project-voodoo and ask for help. Among others, phalanger takes care of me. After trying various methods (ROM Manager, Odin, SGS Kernel Flasher) I flashed the speedmod-kernel-k13c-500hz-CWM kernel (dl from xda) with Odin. This worked flawlessly, and I now can boot into CWM recovery.
Here it get's weird. I applied the lagfix (converted to ext4), which worked smoothly. Quadrant scored 1300 points, "mount | grep -i ext4" returned something and the system was snappier. Cool, I thought, let's see what happens if I now run the Voodoo .zip from the CWM recovery, which I did without reverting to rfs. It worked, but it reset my firmware.
So I again flash speedmod with Odin, revert to rfs (data, cache and dbdata are now rfs) and restore a backup from before the lagfix (all this in CWM recovery). The phone is back to "normal", I have all my apps and the speedmod kernel, but of course no ext4! And now Quadrant still scores around 1200 points, how is that possible? I now again used SGS Kernel Flasher to flash the Voodoo Kernel to give me the audio options, what seemingly works, but I'm very confused.
Why can't I run the Voodoo lagfix, why do I still have < 3e > recovery and why isn't the phone running faster?
Click to expand...
Click to collapse
OK for me, you are confusing the hell out of yourself by doing too much at once.
If you are willing, then I would try the darkys resurrection method, I KNOW this will install the kernel and also initiate lagfix, as you indicated, you should hear it talking to you during the long boot.
With you doing so many things at once, not sure where the issue may be, but try the above and see if you get the same results as most people do.

Heh, that's true, too many things at once.
I looked at the Darky's ROM Resurrection Edition tutorial and noticed something. The attached image is from said tutorial, and when I flash a kernel with Odin it says Removed! before Completed...
Is that an issue?

Davestar2000 said:
Heh, that's true, too many things at once.
I looked at the Darky's ROM Resurrection Edition tutorial and noticed something. The attached image is from said tutorial, and when I flash a kernel with Odin it says Removed! before Completed...
Is that an issue?
Click to expand...
Click to collapse
THAT threw me as well, I 'think' all it is referring to is the fact it has 'removed' the serial port interface (USB) when it does the reboot.
The reason for suggesting darkys, is the lagfix thing, if you don't need to use it (I don't, mine is fine without it) then you can also try this one
http://forum.xda-developers.com/showthread.php?t=926399
This fixed me up when I did a boo boo, learnt me a few things in the process as well.
At some point, I will make my own install and instructions, I used to write technical instruction manuals, maybe I need to do some for here LoL

I tried the resurrect ROM, didn't work as planned. Step1 worked fine (basic ROM) but it wouldn't install the CWM recovery with the Voodoo kernel, and as a consequence it of course wouldn't let me run the resurrect.zip in the second step.
I now reverted to JPY (2.2.1) from Samfirmware, installed the speedmod kernel via Odin and will shortly flash the Darky v9.2 from the internal SD. We'll see how that works.
I think the whole trouble is caused by the JS5 bootloader, maybe?!
The fresh JPY scored 1326 points in Quadrant...

Okay, with the CWM recovery (thanks to speedmod kernel) installing the v9.2 Rom from the SD worked fine. I'm now running 2.2.1 I9000XXJPY with the 2.6.32.9 Voodoo_stable_5.4.1 kernel.
Now I again have the problem that I don't have the CWM recovery. When I enter the recovery it's plain old <2e>. What's going on here?!

Davestar2000 said:
Okay, with the CWM recovery (thanks to speedmod kernel) installing the v9.2 Rom from the SD worked fine. I'm now running 2.2.1 I9000XXJPY with the 2.6.32.9 Voodoo_stable_5.4.1 kernel.
Now I again have the problem that I don't have the CWM recovery. When I enter the recovery it's plain old <2e>. What's going on here?!
Click to expand...
Click to collapse
reflash the kernel

Tried that, maybe 20 times, to no avail. Different methods, from withing speedmod CWM recovery, SGS kernel flaser and Odin. Nothing.
Now back to JPY with speedmod and lagfix. Scoring around 1300 with Quadrant. I Don't think I'll flash anything till 2.3 comes out...

Davestar2000 said:
... I Don't think I'll flash anything till 2.3 comes out...
Click to expand...
Click to collapse
Dang: http://forum.xda-developers.com/showthread.php?t=974117
Edit: The irony...had I checked samfirmware maybe an hour later...

[BOOTLOADERS]CUSTOM Gingerbread Bootloaders for Vibrant - UPDATED [22/06/11]

NOW WITH CUSTOM BOOTSPLASHES! MORE TO COME SOON...
All you guys, PM me any images you want as boot splashes, and I'll see what I can do...
SAFE TO FLASH, IF PROCEDURE FOLLOWED PROPERLY AND NOT INTERRUPTED
SOLVE YOUR RECOVERY AND RAINBOW PROBLEMS ON GINGERBREAD ROMS
WORKS ACROSS FROYO AND GINGERBREAD ROMS BASED ON SAMSUNG GALAXY S I9000 OR SGS-T959.
ALSO WORKING PERFECTLY WITH CYANOGENMOD AND MIUI​When we got Gingerbread ROMs, we also faced the issue of not being able to see the Recovery on the GB Kernels and having to see our screens go funny which were safely called Rainbows! Well, no more !! Flash these Gingerbread Bootloaders and there you go, no issues on Gingerbread except GPS!!
If You can ODIN to JFD, and can see the Download Mode, You can do this.
PLEASE MAKE SURE YOU'RE RESPONSIBLE FOR ANY USER ERROR. I HAVE THESE FILES WORKING 100% ONLY ON A SGS-T959 VIBRANT. FLASHING BOOTLOADERS IS RISKY IF YOU DON'T KNOW WHAT YOU'RE DOING. HOWEVER, BASIC KNOWLEDGE AND COMMON SENSE MAKES IT SURE YOU WON'T GO WRONG WHILE DOING IT.[/CENTER]
This is a small attempt to create bootloader only flashables similar to EZ Boot on the Galaxy S forums, however for our T959 Vibrant... These bootloaders will only have the Vibrant Boot logo and not the I9000 logo, hence maintaining the original look of your phones...
Both the tar packages contain sbl.bin, boot.bin and param.lfs files and have md5 checksums to maintain file integrity when flashing with ODIN. They're working 100% for me... I flashed them atleast 5 times alternatively between them on 3 different ROMs before uploading. So yes, I know the packages are correct.
Gingerbread Bootloaders - No Rainbow - Fully visible Recovery on all ROMs]
Benefits - No more rainbows on Gingerbread 2.3 ROMs like Simply Honey GB, LiDroid, Asgard, etc.
Convenient Key Maps for entering Recovery and Download Modes. (I personally like these mappings over the Standard Vibrant Mapping as you can enter download mode directly without needing to turn off phone or remove battery etc...)
For Recovery - Lower Volume Key + Power Button
For Download - Upper Volume Key + Power Button
Froyo Bootloader - Revert to Vibrant
Benefits - Original bootloaders to revert to stock for Vibrant based ROMs. Also, for MIUI and CM7...
Key Maps
For Recovery - Both Volume Keys + Power Button
For Download - Both Volume Keys and Connect USB Cable
How to DO
ODIN Guide
Please follow this step by step, else I won't be responsible for any DAMAGE.
1. Enter Download mode on your phone.
2. Open ODIN on your computer.
3. Plug in USB and check if ODIN recognizes the phone.
4. Remove all ticks from ODIN, except PDA.
5. Select PDA and browse to the bootloader TAR package file you wish to flash.
6. Click on Flash.
7. If ODIN says PASS, long press power for 10 seconds and it'll reboot, else, repeat 2-6 again...
Avoid exiting download mode if you think the flashing wasn't correct. If however, the peogress window did not start flashing any file, you might just manage to safely reboot and re-enter download mode.
Please note, you do not need to use the PIT file since it will be used automatically from the native partition on the phone.
ODIN shall automatically verify the integrity of the tar package using the included md5 hash. However, for personal prudence, I'd suggest you do that before hand.
CUSTOM GINGERBREAD BOOTLOADERS DOWNLOAD LINK
1. Green Android Logo
- Mediafire Download Link
- MultiUpload Download Link
MD5 Sum - ab17ca277adbc3cd355d7f31ff89bee9
2. Rainbow in my Eye
- Mediafire Download Link
- MultiUpload Download Link
MD5 Sum - 42f2c260b6aa272592dd1f0f3cd77f0c
GINGERBREAD BOOTLOADER DOWNLOAD LINK
- MultiUpload Download Link
- Mediafire Download Link
MD5 Sum - b34df5c2db723eacc534013a011885ad
JFD ODIN File - For use after installing Gingerbread Bootloaders
http://www.multiupload.com/HRYJKFLKFQ "Thanks to laylovj"
MD5: 977E2136996E7138945447A8245D6776
If you have Gingerbread Bootloaders installed and you end up ODINing to stock (JFD), you will notice it changes the bootsplash to I9000. You can either reflash a GB bootloader again, or simply use the ODIN package above to do so.
VIBRANT STOCK (FROYO) BOOTLOADER DOWNLOAD LINK
- MultiUpload Download Link
- Mediafire Download Link
MD5 Sum - 754ecbd8e76d4f81bec49240031f3262
Video
The video here shows Galaxy S i9000 after ODIN. That is because I forgot to include the corrected param.lfs in the packages... However, its been included in the above packges.
Donation Link
I don't demand any donation, but if you think I helped, you may buy me a crate of beer, or contribute to my SGS II kitty by hitting the donation button under my Username. Thanks !!

Frequent questions / Additional Information
Reserved by OP:
DISCLAIMER: IT IS UNSAFE IF YOU ARE A NOOB! TAKE OFFENCE AND DON'T FLASH IT, RATHER THAN FLASH AND BRICK YOUR PHONE
Definition of a Noob
A person who does something to his phone not knowing what he did or what would happen next.
Definition of a DumbHead
All qualities of a Noob + I did not read the OP or FAQs.
FAQs:
1. Is it unsafe?
Flashing a bootloader incorrectly technically bricks your phone. So its like having a single shot at what you're doing, you either keep doing it right and shuffle between the bootloaders, or you do it wrong just once, and you might have a dead phone.
2. What ROMs can I use with the GB Bootloader?
You can use any ROM - 2.1, 2.2 or 2.3 without needing to alter affect your bootloaders as they are backward compatible. However, DO NOT FLASH OR ODIN the following packages
- ODIN Packages containing only an Sbl.bin
- ODIN Packages containing only a boot.bin
If the package contains both, it would technically upgrade/downgrade your bootloader, hence being safe if they are the correct files.
3. Should I flash this before/after flashing a new ROM
You can flash this at anytime, before or after, both are safe.
4. Will it affect performance?
Bootloaders are not known to alter performance. However, on Gingerbread ROMs ported from I9000, they have helped solve the presence of the Rainbow screens, and also allow you to view recovery directly from the phone.
5. Will my 3 button combi work?
If you have the Gingerbread Bootloaders, no. Use the combinations mentioned in the OP to enter both recovery and download mode.
6. Which .pit should I use?
The phone itself has its native .pit partition to take care of any such issues. So not using a .pit file will not affect/harm you. I suggest you not to use one. However, if you do use one, use this - s1_odin_20100512.pit
It is the same we use for ODIN to JFD or Eugene's Froyo that does not brick.
7. What to do when an Official Vibrant update for Gingerbread arrives?
Safest option - Return to Stock Vibrant Froyo bootloaders as in the OP. They will return you to factory bootloaders and any Gingerbread upgrades containing either an sbl.bin or boot.bin or both shall flash just fine. You may choose not to do this, if you're aware of what you're doing.
8. Can I ODIN to stock JFD like I always did?
The JFD Odin packages that I have seen don't contain sbl.bin or boot.bin ! Hence, till that's the case, its safe to ODIN to stock. Please check your ODIN tar packages using 7zip or WinRAR or any other Archive utility for absence/presence of the mentioned files. If they do appear, they should be present together. Else, if they don't appear, you are safe to ODIN to stock.
9. Whatever I flash, I end up in Recovery! What should I do?
Flash stock Vibrant bootloaders, then ODIN to stock JFD. You should be good to go here onwards... I only had this issue when I tried changing bootloaders over MIUI/CM7. Couldn't replicate on Samsung ROMs...

Interesting.

I will wait for someone to flash this.

Great Job Scorp!! Check your pm.

Planning to post a video so that people gain confidence in what's going on really...

adyscorpius said:
Planning to post a video so that people gain confidence in what's going on really...
Click to expand...
Click to collapse
I have all the confidence in the world in you scorp. Take your time man. This is good ****!

is the Gingerbread Bootloader come from samsung officecal ?

paranoia_gu said:
is the Gingerbread Bootloader come from samsung officecal ?
Click to expand...
Click to collapse
Its Official Samsung I9000 Bootloader masked with the Vibrant boot image...

adyscorpius said:
Its Official Samsung I9000 Bootloader masked with the Vibrant boot image...
Click to expand...
Click to collapse
Very nice scorp! You just took a lot the guess work out of the process. Very simple and I feel best thing that could have happened for our phones. Awesome man!

jcc332006 said:
Very nice scorp! You just took a lot the guess work out of the process. Very simple and I feel best thing that could have happened for our phones. Awesome man!
Click to expand...
Click to collapse
Thanks man... Hope people start using it... It's not really that much of an issue really... I've replaced bootloaders over a 100 times over the last week with no issues... And that when I have the phone in India, so if its dead, I cant even get it replaced from T Mobile or the insurance... Lol

adyscorpius said:
Thanks man... Hope people start using it... It's not really that much of an issue really... I've replaced bootloaders over a 100 times over the last week with no issues... And that when I have the phone in India, so if its dead, I cant even get it replaced from T Mobile or the insurance... Lol
Click to expand...
Click to collapse
Man I just flashed and it works like a charm. So dam simple now. Booted up so fast and rainbow is history!

**** yeah!! No more double rainbooows! Thanks waffle dude!
Sent from my GT-I9000 using XDA Premium App

My friend wants to know if she can flash the gb bootloader via sgs kernel flasher or cwm app on simply honey?? She has no CPU.
Sent from my GT-I9000 using XDA Premium App

kooksta said:
My friend wants to know if she can flash the gb bootloader via sgs kernel flasher or cwm app on simply honey?? She has no CPU.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Nopes buddy, don't try that as of now... However I'm planning to upload one for the CwM App soon... Wait for a couple of days... I want to make sure its 100% safe before I release it publically. Till then, you can ask her to just borrow your PC or any other PC to flash it... Just need ODIN and the drivers...

Guess I'll try it out as soon as I flash Simple Honey (downloading it right now).
EDIT: Sweet, worked great, and no more rainbow! Also love the easy way to get into recovery and download. Thanks.

Longcat14 said:
Guess I'll try it out as soon as I flash Simple Honey (downloading it right now).
EDIT: Sweet, worked great, and no more rainbow! Also love the easy way to get into recovery and download. Thanks.
Click to expand...
Click to collapse
Enjoy your phone..

can i use the GB bootloader with a 2.2.1 rom.

paranoia_gu said:
can i use the GB bootloader with a 2.2.1 rom.
Click to expand...
Click to collapse
Yes its backward compatible for Froyo so both 2.2 and 2.2.1 would work...

I flashed gb bootloaders a while ago if I flash froyo ones will my phone brick

CWM Help?

So, just switched out my captivate because my warranty was still in effect. Rooted etc etc. But I remember installing CWM with rom manager to begin flashing my first rom back in the day.
But anywho, I have installed ROM Manager, clicked to flash CWM but when I go into recovery (vol + - & Power) All I get is the samsung one. (Blue text) and I only have the options to reboot, install packages, clear cache or wipe sd card.
Can anyone offer any advice?

^ Try reinstall packages. U may have to do it twice.

Gotta install the update.zip with install packages but you have signed bootloaders if you're on stock froyo. Odin to 2.1 and install cwm from there. You can find the update.zip for cwm on the cappy forums and just put that on the root of your internal memory to avoid using rom manager. Don't even have to root to flash.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

Hmmmm do you have the stock odin pit file/pda or is the old school odin where you couldnt even do that shoot you right back to 2.1?

^ If u want to go back to Stock Eclair...use the first link in my signature below.

I typically use Odin jf6 one click rev0 from designgears. Its still on the forums I believe but might be dead link. Just make sure it has the pbl and sbl. If you are worried I can upload the one I have used for the past 9 months without fail( but ffailure is always possible, just be sure to follow directions and you should be alright. ) alternatively there is a guide to get to stock jh7 on the forums using the Odin that you have to manually select files for. Should be an easy search. I believe people consider this safer for the newer builds but I used oneclick on my 1010 tons of times and have used it once on my 1012 no problems.
Sorry for the long post hope I helped
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

You all have helped. Thank you so much. Running MiUi again and still loving it.

[Q] i9000 Black screen of Death, But can get into DL Mode

Hi Guys, I have a SGS i9000M, and I used this forum post http://forum.xda-developers.com/showthread.php?t=1379650 to install CWM and ICS 4.0.3. I also installed Semaphore Kernel 1.2.0. It was working great for a month until I was messing with the Semaphore settings and enabled Bigmem, then when I rebooted it was stuck on the Semaphore Kernel screen, I couldn't get into CWM, but I could get into Downloading Mode.
I Run Odin 1.85 and select my I9000UGKG3-homebinary.tar file to go back to stock and when I do, I get the message: Cannot open the specified file (Line 1876). I have downloaded 3 different versions of that file, so I know it's not the file.
I've tried every combination of buttons I can, but it's not going into CWM, I just get the black screen of death whenever I reboot any way other than into Downloading Mode.
Can anyone please help me? Thanks!
*Edit: I flashed the PIT, PDA, CSC of the JVP Rom from the above linked post, and got it going, flashed chainfire, it works fine up until then, but when I install the ICS zip, it just flashes some installing stuff, then reboots, over and over, never completing, please help! I've tried different downloads of ICS 4. To repeat: It works fine installing Gingerbread and chainfire, but ICS gets stuck in a loop during install!

I remember something similar when I first flashed to ICS.
I just popped the battery out for a bit, not too long, and then re-flashed the ICS ROM. I was using the teamhacksung rom.
You could try flashing cm9 nightly (galaxysmtd), and Google Apps, and the cm7-kg3 modem.
I can't emphasize enough that you have to read, read, and re-read so that you do it exactly as written. There are lots of youtube videos that may aide you seeing what the "word instructions" mean.
Persist and you will get there.
As the the op says in the second thread of the link you quoted:
if your upgrade to ICS fail
do not despair...
just repeat the Odin steps to get back to KG3 stock + CWR
and flash another ICS build
A further thought may be that you do a factory reset at the beginning of your process. Make sure anything precious is saved to your external sd card.

Hi there, thanks for your reply. I will try your suggestion of the factory reset at the beginning. *Edit: tried, and same problem. When I go to flash stock rom I9000UGKG3, error Line 1876.
The problem i'm having is I can't flash back to KG3 stock, when I try to flash I9000UGKG3-homebinary.tar file to go back to stock, I get the message: Cannot open the specified file (Line 1876). All I can do is load the JVP rom. I have tried multiple different downloads of my I9000UGKG3 stock rom.
I've left the battery out overnight, and tried to flash all different versions of ICS multiple times. I do agree with the 'try again and wait' theory that goes with this stuff, because it works, but in this situation, it gives me the same error 1876 every time, I can't flash back to stock. That might be why I can't install ICS.
I was able to do all of this first time before and ran ICS 4.0.3 with Semaphore Kernel for a month before I messed it up.
Anyone know any other ways to get back to stock?
Thanks!

Hi,
Here some stuff I had in my notes, I'm just copy/pasting, excuse the repitition.
Ditch the i9000m stock rom (which is UGKG3 2.3.3, the one you're probably using) and flash JVT (2.3.5) stock rom, then flash CF-root for JVT. The Bell i9000m will run on the International i9000 firmware and this should get you out of the bootloop.
http://forum.xda-developers.com/show....php?t=1102881
Follow the instructions on here. Use the JVT 2.3.5 PDA, KG3 modem, and csc...its the canadian one. And you might as well repartion with 512 pit. All this can be downloaded on the link above. After you do all that you will have the latest gingerbread firmware. Now you can root with a JVT kernal like semaphore or CF root. There are also a bunch of custom roms you can use on JVT not much if anything for I9000m . The only thing you need from I9000M is the modem and csc....otherwise your cell coverage will suck. I assume you already have odin, if not its available on the above link aswell.
I remember ODIN flashing JVU before going to ICS. Just wanted to see what the value pack was all about.
PDA - use JVT/JVU
Phone - KG3
CSC - KG3
PIT - 512
Re-Partition - ON
Auto Reboot - ON
F. Reset Time - ON
---------- Post added at 01:47 PM ---------- Previous post was at 01:36 PM ----------
Here was something else in my notes:
Recovery
Mounts and storage - Format cache, data, and system
Flash stock

Hiya, thanks again for your reply. I also live in BC, Vancouver.
I will try your further suggestions, thanks so much for sharing your notes.
The link included seems to be dead, any chance to find the thread it would have pointed to?
Cheers.

Here it is:
[Firmwares]Official I9000/I9000M Firmwares collection [Latest: XWJW6, XWJW5, XXJW4]
I'm in Kelowna-fornia.

fixed - ICS install issue
That's sweet, Kelowna is a nice area :>
Well, I worked my butt off for almost two weeks, 4 hours a night.
I should start off by saying I still cannot boot to Clockwork Recovery with any button combination, i've tried all the usual suspects and then some atleast 50 times, probably way more. The only way I can is once in awhile a miracle occurs and it reboots to Clockwork Recovery 5 (the blue text themed one), or if I install CF-Root and use to reboot into recovery in it's options.
I should also mention that whenever I do get into Clockwork Recovery, it's like version 3, with the orange text theme. And I don't know if it helped, but I am now using Odin 1.87 instead of 1.85.
I was finally able to flash stock by flashing the 4 separate files, 512 Pit, PDA, Phone, and CSC rather than flashing the UGK3homebinary.tar.
I tried multiple different versions of Gingerbread with CF-Root to try to get ICS or CM9 working, JVT, JW1, JVU, all of them worked, but the same thing happened when going to install ICS, and even CM9, the install would start, once it got to the part where it says "Rebooting if necessary" on the ICS or CM9 install, it would reboot, show the install beginning again, then reboot at the same spot, infinitely. I made sure to try atleast 50 times so I could bypass the suggestion of trying again.
During this process the phone was acting very buggy, you know what I mean, restarting, freezing, force stops, mounting storage issues. I went into the options and set the phone to factory default, also during another miracle one time it booted to the stock android recovery, you know the one with like 4 options. Format, Wipe, go back, reboot. I formatted and wiped from there as well. These two things seemed to help alot, and the phone was less buggy and more willing to receive my treatments.
After browsing some more, I found this kernel cleaner, i'm surprised no one in the forum mentioned it to me, perhaps they were angry I hadn't discovered it on my own. In any case it's called 'Ultimate Kernel Cleaning Script - 4.0 [MIUI/CM7 and SAMSUNG]', there is one for Samsung Roms and one for CM roms, and all you do is run it to clean out the old before installing ICS. Link: http://forum.xda-developers.com/showthread.php?t=1166954
Ok, so I am now I am excited, this tool looks like my answer. I flash stock, install JVT rom with CF-Root for JVT, (I run my sweet kernel cleaner zip I found) and go for ICS 4.0.3 install.....and same thing happens, sigh. Flash stock again, and oh what's this? I found another custom ICS Rom I can try, remICS http://forum.xda-developers.com/showthread.php?t=1687727
Ok, so I flash stock again, install JVT, CF-Root for JVT, install remICS and....D'oh! Same thing, it's rebooting........but wait, this time it's rebooted into Clockwork Recovery 5 on it's own without any keypress, instead of looping. What a great time for that Miracle! (This only happened 3 times in about 60 hours of working on the phone!) Ok, but what to do now? Well, ICS didn't really install, it just started to, maybe i'll try to restart the install from in here! Choose install zip, this time I chose remICS only because so far it had the lesser fail rate - I didn't want to mess up this golden opportunity, I know it's just a different version of Clockwork popping up, but when anything different than the same failures happens, you don't want to waste it. It's installing....complete! Do I dare risk installing a customer kernel and destroying all of my progress? Yes! Install Semaphore 1.2.6 for ICS, working great!
So, I don't know if it was the kernel cleaner, the remICS, or the miracle Clockwork 5 boot, but I don't want to take anymore chances, that's how I got here, fiddling with what's working great already.
I probably didn't need to post this, but I wanted to recount my experience for anyone else having a similar problem. I have now been running stable with all my apps installed for 12 hours. I would like to have stock ICS with phone rooted, but I don't want to take any chances. This remICS custom rom is very nice, speedy and alot of the bloatware removed, along with some killer SGS3 menus and layout.
I would like especially to thank my Canadian friend for helping me :victory: