Database Develop

[Q] Captivate Boot Loop after Odin one click

Hello all and thx in advance.
ATT Captivate batch 1010
I had Cognition 2.3 I think on my phone and it worked great however I wanted to try a different ROM so I attempted to restore my phone to stock using ODIN one click. I realized after that that I never disabled the voodoo lag fix or deleted my user data.
Now I am stuck in a boot loop that either shows the white ATT logo screen flashing every couple seconds or the phone off charge screen re starting every couple seconds.
I bought a USB Jig and it works great so I can get into D/L mode easily but I have tried flashing the stock firmware at least 6 times now using different machines, different ports, different versions of ODIN and I've searched around these forums and others for several hours trying to find a solution. It seems that I needed to erase my user data in recovery mode and removed the lag fix before I did this but it is what it is. I have tried to get to recovery mode to no avail. All I can get to is download mode.
Any ideas on what I should/can do?
any help will be greatly appreciated.
Rob

Aircraft123 said:
I realized after that that I never disabled the voodoo lag fix or deleted my user data.
Click to expand...
Click to collapse
Neither are necessary for Odin use.
ATT Captivate batch 1010
Click to expand...
Click to collapse
I think that you may need to use the Froyo Odin (JI6).

http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
CM7

please help, i have the same problem, was flashing back to stock from a serendipit 5.12 so that i could get the 6.0 version... all went as planned until odin said "reset" which was my cue to unplug and that the process was complete.... i unplugged the phone and tried to reboot and now it does exactly as the first post described, at&t logo then black screen, then back to the at&t logo then black screen again... my computer doesnt recognize my phone none of the methods of getting to download screen will work... no matter how many times i pull the sd, sim, and batt, no matter the button combination i use or which order i use them in.... same result... i cant afford a new phone i need help, i will donate also... i knew this stuff was over my head, but "curiosity killed the cat" i guess...

I had the exact same problem. Try this method, it's the one that worked for me when all others failed... But remember to follow it EXACTLY.
1. Pull out the battery.
2. Hold Volume UP+DOWN (Don't let go of them until you see the download screen).
3. Stick in the USB (which is connected to the computer).
4. Put the battery back in.
If not, you might need to get a USB Jig.

That Froyo Odin link worked!
Thanks guys I flashed to Froyo and it worked!
I've since flashed clockwork recovery and gotten Serendipity 6.1
As far as getting into download mode I had to use one of the USB jigs.
I ordered one from the guy who does the rom reviews but you could make one as well.
On another note the new ROM seems to be discharging my battery really fast
Before I start investigating it as a problem I am going to charge it completely then let it discharge completely to calibrate it.
Thanks again guys
Rob

I just fixed mine last night, I had the exact same problem because of the exact same upgrade. What you need to do is get or make a usb jig. There's a couple resources around here for how to do it.
Here's a video showing how to make one:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
Once I got my phone into download mode, I used Darky's ROM Resurrection Edition ( http://forum.xda-developers.com/showthread.php?t=940671 ) to restore my phone. Just scroll down to where it says "Files Needed" and download the Captivate version. Once you have that downloaded, use the jig to put your phone into download mode and follow the directions in the Darky's video (jump to about 2:30 into the video). Once I had my phone booting, I used clockwork to install Serendipity 6.
Hope that helps you as much as it helped me!!

went to radio shack, got all the stuff to make a jig and i was able to get my phone into download mode! now to try darko...... thanks everyone!

odin doesnt reconize phone

which odin3 are you using? 1.7? or the one click to stock?
you mentioned you had the bootloop problem before, so you should be using odin 1.7 with 2.2 stock.
open odin
get phone into download mode with your nice jig
unplug jig and plug in computer
box in odin should turn yellow.

And make sure you have the correct drivers installed. CRUCIAL.

Multiupload links not working
I'm stuck in the same situation as the OP.
I've been trying to use the method mentioned in the quote below, but the multiupload links are not working for me. I've been trying for 2 days to get to these files.
Breakin' Ranh said:
**Another thing, read the whole thing before doing it! If you're not confident whatsoever about this process, don't do it**
1. Download the following:
I897UCJH2 Firmware
password: samsung-firmwares.com
http://www.multiupload.com/B5OFPPOJFZ
512 PIT
http://www.multiupload.com/I5WICSBFJ1
ODIN3
http://www.multiupload.com/DLS7TWUVPY
Click to expand...
Click to collapse
Here's a link to the thread for more clarification:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36I've
Would anyone happen to have these files and be willing to share them?

^
Have u tried the Odin or Heimdall One Clicks in the development stickied thread ??
Sent by XDA Premium App

Yep, tried the Odin one click - caught in a boot loop with the AT&T Logo. I have yet to try the Heimdall one.
UPDATE
Tried Odin and Heimdall One-Clicks - unsuccessful. I'm think I will need the stock Eclair firmware file with Odin and the pit file.

lllll Nova lllll said:
Yep, tried the Odin one click - caught in a boot loop with the AT&T Logo. I have yet to try the Heimdall one.
UPDATE
Tried Odin and Heimdall One-Clicks - unsuccessful. I'm think I will need the stock Eclair firmware file with Odin and the pit file.
Click to expand...
Click to collapse
You ever get this to work? - I'm in a similar situation. all flashes 'work' but get stuck at ATT on boot. Not sure Eclair is an option or not since mine is a refurbished phone that started on 2.2

ScruffMcG said:
You ever get this to work? - I'm in a similar situation. all flashes 'work' but get stuck at ATT on boot. Not sure Eclair is an option or not since mine is a refurbished phone that started on 2.2
Click to expand...
Click to collapse
If one-clicks aren't working, you might need to grab the full version of Heimdall or Odin and flash a full package. Some of the newer phone builds don't like one-clicks.

^ +1
See this thread...the original Stock i897ucKK4 thread... http://forum.xda-developers.com/showthread.php?p=19587108
Then see post #57 for the regular Odin to use and instructions on what to do with the firmware.
Sent from my SAMSUNG-SGH-I777 using xda premium

[Q] OH NO! Another noob bootloop thread :p

Hello fellow captivate users, I need some help here!
I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.
With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).
So far I've tried these oneclicks-
I897UCJF6 with bootloaders
I897UCKK4 with bootloaders
Plus various other packages that use odin to flash the different parts of the filesystem etc...
I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)
I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!
I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter )
Any help would be greatly appreciated
Cheers XDA Gurus

I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.

ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..
do you need the jig? is the button combo not working? both volume + plug in usb to PC
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/showthread.php?t=1386924
heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.
or...
try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.
give that a shot...

Wow, quick replies guys, thanks.
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with
Click to expand...
Click to collapse
I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
Click to expand...
Click to collapse
I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.
do you need the jig? is the button combo not working? both volume + plug in usb to PC
Click to expand...
Click to collapse
Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
Click to expand...
Click to collapse
Cool, so cable/ports are ok
Code:
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/show....php?t=1386924
Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.
To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.
Thanks again

I must be messing up - having trouble getting into recovery.
Here's what I did;
The links here: http://forum.xda-developers.com/showthread.php?t=1386924 are dead, so I went straight to method 2.
Downloaded speedmod kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.
How long should I hold the 3 buttons down for? (How many bootloops?)
Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?
All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)
**edit
I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.

For button combo to get into recovery--release when u see 1st att screen.
Or
Have u tried Adb (Android Debug Bridge) to get into recovery ??
Sent by XDA Premium App

cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...

Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.
Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
Sent from my FUSIONideos using XDA

TRusselo said:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Click to expand...
Click to collapse
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business

*removed double post

studacris said:
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Click to expand...
Click to collapse
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.

You have to hit enter at the Right moment, it takes practice

Lol, lucky I've got plenty of patience then!
Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?
Am I able to use adb from there to get an update.zip to internal sdcard?
How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!
Also am I right in assuming that because it gets to download mode it is eventually fixable?
Sent from my FUSIONideos using XDA

Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.
Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.
Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?
Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
Sent from my FUSIONideos using XDA

If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.

Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.
There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.
I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course )

How about a non one click?
I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.

Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
Sent from my FUSIONideos using XDA

Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.
I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.
Unless anyone has any other ideas I'm stumped for now.

When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know
Edit: mabey designgears remembers what fix it when cognadian bacon porked it
Sent from my SGH-I897 using xda premium

[Q] Fuzzy TV Screen after flashing wrong Kernel

I have an ATT Captivate that goes into a fuzzy screen after it goes from the initial White ATT World Phone screen. The wrong kernel was flashed on it after I mistakenly read a post trying to upgrade the the Apex rom. If anyone could be of any assistance. I can't get into Download Mode or Recovery mode... but it still turns on. I'll post screenshots if possible.

rodashtoc said:
I have an ATT Captivate that goes into a fuzzy screen after it goes from the initial White ATT World Phone screen. The wrong kernel was flashed on it after I mistakenly read a post trying to upgrade the the Apex rom. If anyone could be of any assistance. I can't get into Download Mode or Recovery mode... but it still turns on. I'll post screenshots if possible.
Click to expand...
Click to collapse
Ouch, so no download mode or recovery mode? Have you tried booting into download from ADB? if you don't know what adb is then don't worry about it. You might try seeing KIES recognizes it, if not, download any ODIN package and see if the ODIN recognizes it, if it does you're in luck! If not, then you might consider ADB: I'm no expert but I'm sure that when you have ADB there is a way to replace the Kernel Image for a proper one. Just out of curiosity, which kernel did you accidentally flash?

It has nothing to do with kernels, you have a GB ROM with Eclair/Froyo Bootloaders
Sent from my SGH-I897 using xda premium

download mode still works even if it doesnt look like it.. er.. wait download mode should still work. scratch that it WILL still work. flash gingerbread bootloaders

Well
TRusselo said:
download mode still works even if it doesnt look like it.. er.. wait download mode should still work. scratch that it WILL still work. flash gingerbread bootloaders
Click to expand...
Click to collapse
The second problem is... it loops after the fuzzy screen. It only stays for 5-10 seconds then goes back to the ATT screen.
I do know what adb is and I've used it a lot especially with my girl's Mytouch 4g. It's just this was a big problem I haven't been able to crack.
I believe the kernel that was flashed was TalonDEV 0.5.1-RC1 from http://forum.xda-developers.com/showpost.php?p=18330648&postcount=5215
Edit: Odin sees it for the 5-10 seconds it's on... but since it's bootlooping... Odin doesn't have time to do anything further than file analysis.
2nd Edit: The battery status comes up when I plug the phone up when it's off... I know that probably doesn't help, but I figure I should give all the information I can.

b-eock said:
It has nothing to do with kernels, you have a GB ROM with Eclair/Froyo Bootloaders
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Its the KERNEL.
If you have froyo bootloaders and a gingerbread ROM, it will still boot into the ROM and work. But on boot, the KERNEL splash screen is that distorted image in the OP, and also recovery is inaccessible because all you get is the distorted image. And as you should know, recovery is contained in the kernel.
If you're on froyo, and flash a gingerbread kernel, not only will you have the issues stated above, but you'll also likely be bootlooping, which is exactly the situation in the op.
OP.. You don't use Odin booted into Android, or in a bootloop. Its used in DOWNLOAD MODE ONLY.
Search for "usb download mode jig" you can make one, our buy one fur under 10 bucks. It'll boot it into dl mode in seconds.
Then go to the top of the development section, find a gingerbread package WITH bootloaders. flash that, THEN proceed with your original plan

Yes or flash gingerbread boot loaders and get recovery back, Then flash and appropriate kernel in cwm.
Hint: there is a button combination that you must preform to enable download mode it is posted several thousand times in the captivate section I would suggest go and find what it is.
Btw. The button combination happens to be posted in three or four of the stickies. And the forum rules say to read stickies before creating a thread or posting.

Listen
TRusselo said:
Yes or flash gingerbread boot loaders and get recovery back, Then flash and appropriate kernel in cwm.
Hint: there is a button combination that you must preform to enable download mode it is posted several thousand times in the captivate section I would suggest go and find what it is.
Btw. The button combination happens to be posted in three or four of the stickies. And the forum rules say to read stickies before creating a thread or posting.
Click to expand...
Click to collapse
I've read them already. I told you I can't get into either mode. I know exactly what the 3 button combination and the download combination is for this phone and since the wrong kernel was flashed on it, it's apparently not working.
Hint: being helpful is great, but when you start talking down to people, you start to become an ass. When that starts to happen, it's best you be quiet and let people who want to come up with a solution to the problem speak.
Thanks.

rodashtoc said:
I've read them already. I told you I can't get into either mode. I know exactly what the 3 button combination and the download combination is for this phone and since the wrong kernel was flashed on it, it's apparently not working.
Hint: being helpful is great, but when you start talking down to people, you start to become an ass. When that starts to happen, it's best you be quiet and let people who want to come up with a solution to the problem speak.
Thanks.
Click to expand...
Click to collapse
You need to get a jig then
Sent from my CM9 ICS i897 Captivate

Thanks
studacris said:
Its the KERNEL.
If you have froyo bootloaders and a gingerbread ROM, it will still boot into the ROM and work. But on boot, the KERNEL splash screen is that distorted image in the OP, and also recovery is inaccessible because all you get is the distorted image. And as you should know, recovery is contained in the kernel.
If you're on froyo, and flash a gingerbread kernel, not only will you have the issues stated above, but you'll also likely be bootlooping, which is exactly the situation in the op.
OP.. You don't use Odin booted into Android, or in a bootloop. Its used in DOWNLOAD MODE ONLY.
Search for "usb download mode jig" you can make one, our buy one fur under 10 bucks. It'll boot it into dl mode in seconds.
Then go to the top of the development section, find a gingerbread package WITH bootloaders. flash that, THEN proceed with your original plan
Click to expand...
Click to collapse
I'll order a jig and see if that gets me into download mode. Thanks for the explanation. I'll update this once I get some results.

Gotcha
korockinout13 said:
You need to get a jig then
Sent from my CM9 ICS i897 Captivate
Click to expand...
Click to collapse
I'm on it. Preciate it.

Fixed!
Got the jig, flashed the right kernel back on, game, set, match... 8 bucks well spent. Thanks everyone.

In future reference, you can force the phone into download mode from adb.
Using Doc's Master ROM v7: Cappy edition

KangKilla said:
In future reference, you can force the phone into download mode from adb.
Using Doc's Master ROM v7: Cappy edition
Click to expand...
Click to collapse
if the phone is in a state that accepts adb coms

[Q] Still dead after Unbrickablemod

I performed the Unbrickablemod hardware modification the other day with a friend. We did it and it showed up as the dev board. I can successfully boot it into download mode and use the one-click install in the thread. (Here: http://forum.xda-developers.com/showthread.php?t=1312391)
But that's where I'm stuck. Heimdall performs the one-click successfully, but my Tab doesn't boot up, and the screen stays off no matter what. I saw someone having a similar issue in the main thread but they didn't post again. Someone else posted that you can get the power strip light up if you unplug it and press the power button a couple of seconds, or if you plug it to the wall charger. Both worked for me too, but I don't know where to go from here.
Any help is appreciated.

can you boot to download mode?

priyana said:
can you boot to download mode?
Click to expand...
Click to collapse
I can't, any key combination with the power key just lights up the touch strip. Nothing on the screen.

what is your device model, any chance you have flashed a wrong firmware into it after it was resurrected?

priyana said:
what is your device model, any chance you have flashed a wrong firmware into it after it was resurrected?
Click to expand...
Click to collapse
It's a GT-P1000 and I used the one-click Heimdall suite provided in the OP. I also tried Turkish firmware I downloaded from samfirmware with heimdall command-line tool. (1.3.1) Still no luck. I'm not sure what I'm doing wrong.

I wonder if you can still make the unbrickable to kick into dev mode again?
And use GB-stock-safe-v5 from overcome instead? (link in my signature)
it is a complete JQ1 (Italian) rom.

Oh, download mode via Unbrickablemod still works, I guess that's the only beacon of hope that keeps me going. I'll try it once I get back from work. I can't use it if it's in Italian, but the important thing is getting the tablet boot up and enter the recovery on its own, right?

It is European ROM, it has English.
But it is stock. If that boots, it is resurrected.
Sent from my GT-P1000 using xda app-developers app

Finally got some time to work on my Tab.
I got the files, didn't know how to use them with Heimdall since the tutorial was written for Odin. Extracted all the files and followed Heimdall's usage. I guess I got something wrong, but magically, the screen came up showing the "Downloading" screen. Then it rebooted into the infamous glowing Samsung logo bootloop with vibration.
I'm now trying to go into download mode, if anything comes up I'll post about it. I have no idea how it worked but now I know I didn't bust the screen somehow when I performed the hardware mod. Thanks!
Edit: I can get it to download mode by itself. Now I need to find a PC with Windows to try Odin. Shucks.

By the way, I tried flashing Technomancer's kernel provided in the Cyanogenmod wiki to instal CM directly, but can't boot into recovery. I guess I need to complete Overcome flashing, then try flashing CM. Does that sound correct?
Edit: Thanks to this tutorial, I have successfully managed to flash Overcome and I guess CWM is also installed. My Tab is finally revived! I'll keep you up to date with the progress on installing Cyanogenmod. Thanks for all the help!
Aforementioned tutorial: http://forum.xda-developers.com/showthread.php?p=34692020

I kept following the Overcome manual, managed to install Overcome kernel and now I got CWM working! It's backing up current Overcome installation right now, I think I'm doing it right.
Edit: It's done! I got CM9 on my Tab and it works great! (Kinda. No official CWM sucks.) But it's great. I'm happy that I turned my Tab back from death. Thank you so much.

Glad it is revived.
Yeah, I am quite dismayed that cm wiki doesn't recommended overcome kernel when it is obviously the one that works best.
Sent from my GT-P1000 using xda app-developers app

After all the headache I endured, I really wish they'd written a more through wiki entry for Galaxy Tab. But Overcome works like magic, and after flashing Overcome, Cyanogenmod installer zip easily flashed newer CWM versions. It's up-to-date and works great. Thanks again! More people should know about Overcome.

[Q] Soft Brick/Bootloop I9000

Hey everyone,
I was asked by a friend to update his moms Samsung GT I9000 (stock rom up until now) to Cyanogen.
I've played around with CM before and figured it would be a piece of cake, but I guess I was wrong.
I've followed this guide to the letter:
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Used the semaphore .tar mentioned in the thread and used Heimdall to flash.
All went well untill I tried to reboot into recovery, step 10: I get a bootloop.
Normal reboot ends up in a loop as well, but I can access download.
I've tried to reflash semaphore with both Heimdall and odin. Heimdall says it's worked but doenst get rid of the bootloop, Odin just didnt recognize the device at all.
So I figured I would flash something else, but what?
I downloaded CM recovery from this site: http://clockworkmod.com/rommanager but it doesnt have a flashable image as far as I can see. (Odin doesnt think so anyway and creating a .tar file doesnt help).
And when I checked this thread for the original software http://forum.xda-developers.com/showthread.php?t=1640906 the links are broken.
I've also tried the JVU mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2247484 and found it here http://download.chainfire.eu/132/CF-Root/SGS/, no luck.
Last but not least I downloaded Kies in the hopes of changing the USB drivers, allowing Odin to recognize the device, that helped. Now Odin can flash, but I still end up in the same bootloop.
There must be something I'm missing here. Does anyone have any idea what else I can try?
Yoora

Anyone?
I've been searching through the forums and I can find about a 1000 ways to get download mode working again, but not what to flash once you get there....
I'm really hoping to find something today since I'm supposed to give the phone back tomorrow. So any help is greatly appreciated.

I think its firmware issue you need full firmware I mean pda phone. Csc