Database Develop

[Q] Phone cycle before bootloader?!

Hi all,
My collegue comes up this morning with his phone which is no more booting.
I'm used with the custom roms stuff and updating using odin and had already saw many posts about Internal SD failure. However the behaviour of his phone is really not as what i red before.
His phone is alway cycling like if the power button were stock, but it is not. Just shows I-9000M then reboot (no "S" or other stuff)
If I try to access recovery mode, it start cycling. If I go to download mode, it works (and not cycles).
So I've used Odin to install Stock Bell JL2 rom (and update the bootloader). It changed nothing.
Also tried to roll back JH2, with pit 512 and repartition, update bootloader. changed nothing!
then re-up JL2... changed nothing!
So he is leading to Bell service center now... but have you ever seen that?
Thanks!

Hey, im stuck with the EXACT same problem. Ive tried everything too. unfortunetly, i don;t have a receipt, so i can't go to bell
Still searching and asking... just hoping. lol.

[Q] Samsung Galaxy s I-9000 Froyo Update problem

hello guys,
Firstly let me state that I am not a very technical person.
Here is the problem,
I have the above phone on Eclair 2.1, plugged it into Kies and Kies offered to update to the latest firmware which is obviously Froyo 2.2.
Everything went fine, the phone rebooted and it appeared that the software had installed correctly. However, I noticed that I could not get any signal, not just that but the phone is now stuck in flight mode.
When I go to Wireless & Network --> Mobile Networks it does not even let me into that option. It says "Insert Sim card - Insert Sim Card to access Network Services".
On top of that, when I click on About Phone --> Status there isn't even an IMEI number!
I have tried to rollback the upgrade, tested the sim card in another Galaxy S (it works fine) so I know this is a software problem.
Does anyone out there have any advice so I can get my phone working again?
regards
Chris

Remove sim card and sd card then factory reset then set up as a new phone would be my first step .
jje

Hi there,
Firstly thank you for your help.
That step did not work, I just tried it. So what would you suggest now?
I was thinking of re-installing the firmware again...thing is Kies won't allow me to do this again as it already thinks the firmware is up to date.
This is a really bizarre problem...any further suggestions?
Thank you in advance

Two choices one take it to Samsung for repair as Kies broke it .
Second choice would be to invalidate your warranty and flash basic stock rom via Odin this would be at your own risk .
http://forum.xda-developers.com/showthread.php?t=723596
jje

[Q] trouble with my Sasktel Galaxy S

I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)

I am also on sasktel and am an impulsive flasher (1-5 times daily) Heres an easy, fast fix. GO here:
http://www.darkyrom.com/community/index.php?threads/guide-installing-rc5-easy.2382/
go to section enabled "For GT-I9000 users only" and follow step by step. You can stop at step 2 if you want to leave your rom stock samsung or do last few steps to have darkys on there. EIther way once done you'll also have to enable the 850 band *#2263# then enable wcdma 850 option. Also you will have to manually enter your APN under network options. I use inet.stm.sk.ca for sasktel. Note that the Ficeto_JVB.zip download there includes all needed to flash (.pit file, rom, odin). THis is always my fail safe method after boot loops ( I always screw something up playing around lol).
ps: also depending how desperate you are and how trusting you are, I work at sasktels head office in the cornwall and if you wish I am sure I could take 15 mins out of my day tomorrow to do this for you, although you will not be able to get through security so you will have to trust me taking off with your phone lol. email me at [email protected] if needed.

trouble is I can't put things on SD card because I can't get it to load android

You won't be able to load eclair through Odin because JL2 installed a new SBL (secondary boot loader). Go to samfirmware.com, download JL2, and use odin to flash that. Once that's flashed it should fix your issues. Then, if you want a custom ROM, try the romkitchen (romkitchen.org).

problem solved!! turns out darkyrom did fix my phone, I couldn't push the zip file to my phone but their tar file got my phone working! Thanks for all the help

Dougustine said:
I tried to use ROM manager to update my rom to overstock, this did not work so well. It installed fine but then the battery refused to charge and all sorts of wierd problems so I used my backup to uninstall and that failed. I downloaded Odin3 v1.7 and downloaded the original stock firmware(eclair) and that failed. I then used UGJH2 and the phone will boot and see the galaxy s load but then the screen goes blank and vibrates periodically. in the recovery (3e) it says Can't mount /dev/block/st110. The last official firmware install was KC1 through kies but I can't find that anywhere is there any hope for this(sweating cause wife might find out)
Click to expand...
Click to collapse
I loled, I've been in the same boat, wife is always asking me why I always have to mess around with stuff. Shoulda seen her face after I soft bricked the phone the first time.

Just rooted my phone
I am new to this, I can do all kinda of things with my pc but with my phone a different story lol. I don't understand when you say "Eclair". Is that a different model or is that stock. I am too from sasktel.

Android 2.1 is Eclaire, 2.2 is Froyo and 2.3 is Gingerbread... Ice cream is next 4.0

hi guys, I know this is an old post but has anyone successfully unlocked their Sasktel i9000 vibrant without paying any unlock code service? has anyone tried anything like the SGS Unlock Pro that claimed to unlock all GSM galaxy S phones but did not list Sasktel? anyways, from the sound of it is Darky's rom currently the best for i9000's? I wanted to try CM9, so i did the super 1 click root and followed the CM wiki page to push clockwork recovery to the phone through Heimdall Suite but both times i tried failed and stuck in a boot loop so both times i ended up going through Odin to fix it. (super 1 click root didnt seem to stick b/c i lost superuser after fixing the phone w/ Odin, is that normal?)
anyways i had a very unique situation, originally had a Bell i9000m but died 1 week later tried to fix it numerous times for 7-8 months ( i live in U.S., and Sammy refuse to fix it b/c i dont have a canadian address they can send it back to b.s.) anyways finally landed myself a dead i9000m w/ broken screen, so i took both apart and put the working parts together. now 1 working phone with 3 problems: 1) so it seems that it's currently locked to Sasktel (it can be done but i'm curious if there is a cheaper way or even free) 2) CM wiki suggested Heimdall push CW recovery cause boot loop (some on xda suggested flashing the phone back to 2.2 (or 2.1??) first) 3) i was playing around and click on screen update and lose my touch keys ever since (ppl also suggest flashing it back to 2.1 and reupdate the keys, but will a bell i9000m 2.1 stock rom be compatible w/ the i9000m from Sasktel?)
anyways lots of questions there but if anyone can answer anyone of these would be greatly appreciated.
thanks in advance
Update: problem 1 is taken cared of. SGS Unlock Pro worked like a charm. tested, working. other 2 problem still unsolved.

RESOLVED [Q] SIM not detected?? (ATT + polish GNOTE)

I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?

I had a similar SIM card issue when I tried to activate the 1700MHz band in Service mode (for fun). Wipes and stuff didn't solve anything. The way to revert it for me was flashing a full stock Samsung firmware in Odin.

Can you provide more details on how you did this?
Where does one get a full stock sammy note firmware?
Are there some good instructions on this?
I have flashed my SGT via odin several times. Same odin? Same process?

In the development section you will find some versions.
The key for me was flashing a new Modem (Radio/base band) image via Odin I think. I changed Kernels and ROM's but only flashing a ROM including the Modem got rid of my SIM issue. Not sure because in the end I flashed a full N7000OXAKJ1 firmware in Odin from here:
http://forum.xda-developers.com/showthread.php?t=1310513
It did the trick, though the tread is dead. I think any ROM including Modem might help, I currently running the 2.3.6 N7000ZSKK1 firmware and it is great, also included a Modem.
http://forum.xda-developers.com/showthread.php?t=1342797

fwelland said:
I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?
Click to expand...
Click to collapse
when this happened to me, also due to turning on 1700, I was able to reset my phone by doing a factory reset. Unless your modem.bin is corrupted, you should not have flash a new rom.
- frank.

ugh....
you mean factory reset via Settings->Privacy->Factory Reset?
Tried that... No affect. Is there another way to do this?
Was hoping to fix w/o the flash. NOTE: I did go into that service menu with the 3G Freq are listed. I was curious when I saw the post. But I never changed anything. Just saw the screen and thought "neato". I wonder if there is another service screen that has an option for 'unfuck'???
Still searching for answers, before trying the ROM route...

fwelland said:
ugh....
you mean factory reset via Settings->Privacy->Factory Reset?
Tried that... No affect. Is there another way to do this?
Was hoping to fix w/o the flash. NOTE: I did go into that service menu with the 3G Freq are listed. I was curious when I saw the post. But I never changed anything. Just saw the screen and thought "neato". I wonder if there is another service screen that has an option for 'unfuck'???
Still searching for answers, before trying the ROM route...
Click to expand...
Click to collapse
Here is Chodthewacko posted about it:
http://forum.xda-developers.com/showthread.php?t=1335920
Factory reset and toggle band settings seems to have worked for him. I got frustrated and Odin flashed everything, that worked for me.

whoa....
when I try that procedure (* # * # 1 9 7 3 2 8 6 4 0 # * # * ) I get a pretty empty screen...can't do much of anything...just some useless buttons on the bottom of screen when I select the menu button...
I think I recall seeing another number for doing a similar thing...

fwelland said:
I got a GNOTE from negri on 11/9. It seems it was s polish version. It has been working wonderfully on ATT (after adding in APN manually for 3g/H+ -- voice worked out of box).
I rebooted Today (11/13) and now it has the crossed out circle instead of bars and says "Insert sim" when I start to do cellular related activities.
I have Seated and reseated; nothing. pulled the sim and put back in my SGT (phone enabled) and it works. Put back in GNOTE, still no sim detected! Stuffed SIM in my N1; it works.
Any suggestions?
Click to expand...
Click to collapse
OMG I have the EXACT same issue as you, and I got mine from NEGRI also! It was working perfectly until last night --- all of a sudden I got that circle and I've been trying to fix it since then! Please keep me posted if you find a solution, I was going to try and contact Negri tomorrow for an RMA.

still nothing.
I did a root. No changes...
I did a rom flash of kk1 ... no changes....
I was trying to reflash the modem with KJ6 modem....but have a signature failed problem...
now what???

I solved my issue by a combo of those steps.
I did full flash in Odin of jk1. When I rebooted that didn't solve things so I wanted to flash the other recommendation, kk the Chinese rom.
Upon entering recovery I noticed I lost 2e and was on 3e. So I had to download chainfire's rooted jk1 kernel and do that zerg rush to get root. It was while I was doing that that suddenly my similar got recognized. By the time it finished installing the rooter kernel I had full reception again. I flashed kk just for good measure and its been smooth since. Hope it works for you too and I'd love to know what the heck broke it in the first place??
Sent from my GT-N7000 using XDA App

hi fwelland, it's hk1981...so you tried the rom flash and it didn't work?

Hi hk1981,
No the KK1 rom flashed fine. By all accounts it works well, except that pesky phone part. This KK1 rom is really 'clean' and very little bloat-ware and it installs a vanilla boot animation (not a carrier one). All that is nice, but didn't help my problem
I did notice a peculiar thing: while in recovery (android recovery, not cwm) I get some warning about "CSC something or other, fixing".
I have a short list of things to try before I have exhausted my DIY options -- the post just above looks promising.
I think the answer is out there. We just need to keep looking and keep attention on this thread and others like it. This place and others like it are a huge help and I'd like to solve it and then give back a good set of instructions.
FWIW: I wonder if there was some voodoo in the polish rom that caused some issues in the modem when a different than expected sim was installed? Or if one of those funky polish apps that updated it self before I could turn off auto-updates has something to do with it (doubt this -- I don't think apps can do stuff unless rooted...)...
Still searching....I got this other pesky problem to deal with now: w-o-r-k

fwelland said:
Hi hk1981,
No the KK1 rom flashed fine. By all accounts it works well, except that pesky phone part. This KK1 rom is really 'clean' and very little bloat-ware and it installs a vanilla boot animation (not a carrier one). All that is nice, but didn't help my problem
I did notice a peculiar thing: while in recovery (android recovery, not cwm) I get some warning about "CSC something or other, fixing".
I have a short list of things to try before I have exhausted my DIY options -- the post just above looks promising.
I think the answer is out there. We just need to keep looking and keep attention on this thread and others like it. This place and others like it are a huge help and I'd like to solve it and then give back a good set of instructions.
FWIW: I wonder if there was some voodoo in the polish rom that caused some issues in the modem when a different than expected sim was installed? Or if one of those funky polish apps that updated it self before I could turn off auto-updates has something to do with it (doubt this -- I don't think apps can do stuff unless rooted...)...
Still searching....I got this other pesky problem to deal with now: w-o-r-k
Click to expand...
Click to collapse
I had that problem too, it doesn't detect that CSC and then goes ahead and applies something. Check to see if you are in 3e recovery, I think you are after having flashed vanilla JK1.
Re-flash Chainfire's rooted kernal for your appropriate version and then go back into recovery and it should be 3e and you can flash thru CWM then.
Also note; each time I flashed, I also wiped data/cache/davlik just to be sure.

yes it does say:
Code:
Android system recover (3e).
So I will need to try the methods you (crippenx) suggested.
FWIW, the CSC message that I get when I first enter recovery is:
Code:
# MANUAL MODE #
--Updating application...
Successfully update application.
--Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'TGY'
Sucessfully applied multi-CSC.
I have no idea what this means. It does it every time I enter recovery.
FWIW, I never flashed this gnote with ODIN (I have used ODIN on my SGT several times). I got to KK1 by first rooting via http://forum.xda-developers.com/showthread.php?t=1329360 (using 'forget the above steps') and then using the CWM 'kk1-wipe.zip' from here http://forum.xda-developers.com/showthread.php?t=1342797 -- I didn't use ODIN to get to kk1.
I see on the Root/Unroot thread, there is a KK1 kernel option for 'simple'. I think I will try that with rooted already script.
But I am open to any/all suggestions...
Code:
Baseband
N7000XXKJ6
Kernel
2.6.35.7-N7000ZSKK1-CL706440
[email protected] #2
Build Number
GINGERBREAD.ZSKK1

fwelland said:
whoa....
when I try that procedure (* # * # 1 9 7 3 2 8 6 4 0 # * # * ) I get a pretty empty screen...can't do much of anything...just some useless buttons on the bottom of screen when I select the menu button...
I think I recall seeing another number for doing a similar thing...
Click to expand...
Click to collapse
My rough guess is that the phone has a list of 'valid service menu options', and it cross references it with what is on the SIM card.
Once the phone decides it's not going to read your sim card, the service menu is blank. This is a real headache.
That's why once I set the 1700+2100 combo, and my phone boycotted my sim, I wasn't able to set it back.
That's really dumb, imho, to have a one way toggle like that. I'm fine for settings to enable/disable other settings, but for a setting to disable itself? ugh.
I would really like to know what's going on. I was planning on switching to AT&T before my next trip (which is soon) but I can't risk my phone glitching out like that during the trip.
Actually, the ROM is on my SD card so I guess it wouldn't be THAT horrible, but it's certainly not something I want to do. Perhaps we just need a way to flash back the modem.bin, assuming it's corrupted.
- Frank

Sorry typo on my part. You are in 3e recovery because of that base flash, now you need 2e recovery which you can get via chainfire's rooted kernel. His installation procedure runs a batch file that uses that zerg rush exploit which I gather is partially from gingerbreak. It was during this procedure that my baseband suddenly came back, my sim card finally detected.
Once that was done, I entered 2e cwm with volume up,power,middle button and did erase of data,cache,davlik and then flashed kk rom via zip file.
Sent from my GT-N7000 using XDA App

fwelland said:
yes it does say:
Code:
Android system recover (3e).
So I will need to try the methods you (crippenx) suggested.
FWIW, the CSC message that I get when I first enter recovery is:
Code:
# MANUAL MODE #
--Updating application...
Successfully update application.
--Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'TGY'
Sucessfully applied multi-CSC.
I have no idea what this means. It does it every time I enter recovery.
FWIW, I never flashed this gnote with ODIN (I have used ODIN on my SGT several times). I got to KK1 by first rooting via http://forum.xda-developers.com/showthread.php?t=1329360 (using 'forget the above steps') and then using the CWM 'kk1-wipe.zip' from here http://forum.xda-developers.com/showthread.php?t=1342797 -- I didn't use ODIN to get to kk1.
I see on the Root/Unroot thread, there is a KK1 kernel option for 'simple'. I think I will try that with rooted already script.
But I am open to any/all suggestions...
Code:
Baseband
N7000XXKJ6
Kernel
2.6.35.7-N7000ZSKK1-CL706440
[email protected] #2
Build Number
GINGERBREAD.ZSKK1
Click to expand...
Click to collapse
For me flashing all partitions via Odin worked (no pit file or repartition). Tried all sort of stuff from recovery first with no result.
I don't know what partition flash from Odin did the trick, but you could try Odin flashing a Modem separately and check if that works. If not try the rest?

Finally got back to this.
After much fusing I finally got KK1 and cwm working. It was odd, I had to re-run the whole root process again.
At that point I could apply the KJ6 modem w/o any problems (via cwm)
no dice!
Still dead!
Not sure where to go next???
Can some one provide a few details about flashing a modem,rom and/or kernel via ODIN? Perhaps that method will work....

fwelland said:
Finally got back to this.
After much fusing I finally got KK1 and cwm working. It was odd, I had to re-run the whole root process again.
At that point I could apply the KJ6 modem w/o any problems (via cwm)
no dice!
Still dead!
Not sure where to go next???
Can some one provide a few details about flashing a modem,rom and/or kernel via ODIN? Perhaps that method will work....
Click to expand...
Click to collapse
Oh when you flashed jk1 I assumed you did it the old way via Odin and the multiple files. That's how I did it and you're right, that may be what fixed it as when I used to brick my sgs and sgs2, it was always a full Odin flash of stock that brought it back from the dead
To flash in Odin put your phone in download mode. Fire up Odin. In csc point to csc file. In phone section point to modem and for PDA you point to the code file. Don't put anything for pit or bootloader and unchecked the repartition toggle.
Connect your phone and wait for Odin to detect it and show yellow in the status window. Press start and you're good to go. Hope this does it!
Sent from my GT-N7000 using XDA App

Need some advice with i9000M

Hi guys, I know I need to make this short but I want it to be clear anyway. This is crazy I wanted nothing to do with smartphones 3-4 days ago because all the carriers rip us off with huge bills to get them. But low and behold when my cheap flip phone died after 3 years of loyal daily work a friend of mine offered me his Galaxy S i9000m for a good price. Started playing with the device and having a strong software/computer background started having a lot of fun with all the applications and was amazed with the possibilities (Networking, ipcam whatever) that just kept multiplying until I fell upon applications that needed something called gingerbread... Anyways I can tell you I learned a ****load in 48hours...
So I installed Samsung Kies, it found me the update and put it on for me.. (2.3.3 Gingerbread) then the nightmare started. The phone would boot, and would randomly reboot a random number of times until it could finally stay on and this could last from 2-30 minutes. So I thought, I'll just do a factory reset, to realise that its "STUCK" in 2.3.3 once its updated no going back to 2.1 or 2.2 easily.
Started looking around for ways to downgrade, and EVERY SINGLE LINK redirects to these 'mass download' sites that end up saying the firmwares were taken down for copyright issues. So desperate to find something, I fell upon a multiple CSC FROYO 2.2 firmware for the i9000 and was able to flash that in download mode the phone worked fine, except for me being very curious about the fact that I lost the "M" in my model description...
So started reading this thread(Mostly because I had already realised that with this non i9000m rom I had lost the 3 button DOWNLOAD MODE which i Had before) **** : http://androidforums.com/galaxy-s-a...flashing-darky-v9-gt-i9000m-minimal-risk.html
Got it rooted, got clockwork on, never managed to get the voodoo kernel working had errors in CWM.. so I was ready to give up until my eyes caught the
"*#*#2663#*#*
Then click Touch key FW update"
Which I thought would be neat to try.
NIGHTMARE, now BACK and MENU are dead, I understand that this is because I am running a non i9000m ROM and that updating the firmware rendered them unusable.
I came accross a post : http://forum.xda-developers.com/showthread.php?t=869492
Where this problem is adressed, I pretty much understand everything that should be done to get this back on its feet (right now the phone is still working I can use it at least 75% of its functions work except no back and menu)
Where I need your help : I'm not too sure how to attack this the right way, since I can't get into download mode I understand flashing is now more complicated to accomplish and now that I know that I need a i9000m firmware how can I find that...
Sorry for the long post I know I'm a noob here but I wanted to prove I had done all my homework to get where I'm at now seeking help from you guys!
Thanks a lot
Mat

By the way : Galaxy S GT i9000m currently on a 2.2 i9000 rom, my carrier is BELL. (Canada)

So there's no way of updating to 2.3.3 using Kies?
The only thing I can think of is getting a USB jig from ebay, which makes the i9000 go to download mode instantly. Good luck!

Alright, so I used CHECK FUS, and was able to get the i9000m stock BELL firmware YAY
now the help I need is to flash it correctly and find a way to get past the no download mode problem, would be very appreciated,
thanks guys
No, similar minds Sepharite, I also thought of redoing the Kies method, and then going back again if I needed to but now Samsung Kies says "Your device does not support firmware updates through Kies" Wow.. useful app, a samsung native app can't even detect it's own fricking hardware.
Thanks

UPdate : Was able to restore the 3 button "DOWNLOAD MODE" with a little tutorial online. Now I tried flashing my i9000m with ODIN, it flashed all the way and I get a i9000M logo now but it gets to the splash S logo and keeps rebooting never gets into the actual android setup is there something I did wrong?
In Odin all I put was the "BELL i19000m stock ROM" under PDA and wrote it. The device rebooted after flash but there still seems to be something I haven't done right.
Thanks guys

Please help guys, I know some of you out there have got this stuff nailed down!

Did you flash with a 1 file ROM or a 3 file ROM?
Using the UGKG3 ROM that you can fine here:
http://forum.xda-developers.com/showthread.php?t=1102881
Place the 3 files in their respective places (PDA, PHONE, CSC), for the PIT file, select the 512 pit file that should have come with ODIN, connect the phone, wait for ID:COM to turn yellow, and press Start.
That should get you going again. You may get apps that force close, so you'll need to delete the apps data and then reinstall them.

Hey thanks a lot man ya my flash was a SINGLE FILE, I bricked it yesterday trying to flash a different ROM since I had nothing to lose, I just got it working again on the old 9000 ****ty version that my back and menu keys don't work...
Now for some reason the USB JIG doesn'T work anymore after a couple of uses... could something have been damaged by doing it many times?
And your original roms section they are all unavailable due to copyright did you check the links before sending them?

When you say get the stock roms, I was able to get the UGKG3 file, but what about the versions? When I look at the north american section of the 2.2 version
UGKC1/UGKC1/BMCKC1/Sbl
UGJL2/UGJL2/BMCJL2/Sbl
UGJK3/UGJK3/BMCJK3
which one of the three suits me?
Thanks for your help, and if I get this running and go back and update my touch key firmwares with the right "Vibrant / 9000M" roms I should get them working again?
PS : I'm also very preoccupied by the fact that the USB JIG fix doesn'T seem to pop download mode anymore because this version of the ROM that I have has Download mode not working with the 3 button method. :S I wonder whats going on, but basically if I get your ROMS working the first time It'll fix everything but if it crashes then I lose the galaxy haha

Not sure why the USB jig doesn't work anymore. I have a couple and have only tested them on my phone to make sure they work, but they did not work on a Galaxy S II that I tried it on.
I just checked and the download link for the UGKG3 ROM at multiupload (downloading from multiupload), still works (you need to enter the captcha phrase).
The site megaupload was shut down by the US gov't, so that one won't work.
EDIT: UGKC1/UGKC1/BMCKC1/Sbl is the latest Froyo release from Bell. That's what mine and my wife's gt-i9000m phones came with.
She's still running it on hers.

Ok sorry for all these posts, basically when you said UGKG3 you want me to get the 2.3.3 ROM on ? Is that right? What if I Want to put on 2.2 to be sure I have no trouble with it since I'm in all this mess because the Kies update to Gingerbread had my phone in a bad state.
Thanks a lot by the way!

Sorry your post refreshed right after I did mine. Alright cool so I'll try the one you say your wife is running, I had made myself a JIG with a stock Samsung wire, it was working fine with a 300K resistor and I decided to solder it on and then it stopped working after that.... maybe the actual "usb plug" is damaged from the soldering heat I guess I'd have to try another wire, but anyway I'll try to download the 2.2 I just got the UGKG3 3 FILE rom downloaded one of the links did work!
But I'm a little worried about 2.3.3
I'll try to see if i can download the 2.2 first.
I mean basically... these roms shouldn't jam during transfer i Guess

One other thing I see different confusing information, is it important for me to click 'update bootloader" with these stock roms since these files contain an 'SBL' ? Because both times I bricked it was with an "update bootloader checked" firmware update trying to put the ARIES 3 button method fix as a boot.bin and sbl.bin
Fanks..

Files with SBL in the name already have the bootloader included in the PDA file, so "update bootloader" should NOT be checked.

That reassures me, because the only times it did jammed was when the bootloader was checked! THanks a lot blackrose i'll go out and buy another usb cable because I destroyed mine making my JIG. And I'll try yours out. I was reading a lot on another thread and found this one guy who flashed the JL2 one to save his keys instead of the C1 you said your wife was running, whats the main difference between those two and which one should I start with?

Update : I got a new wire, flashed the KC1 version of the firmware, everything goes fine, I did a repartition with the 512 PIT, it reboots the phone, loads all files in a prompt in yellow and there are no errors that appear, the phone reboots after writing 'successful update' and then goes to the galaxy logo and jams there and does the ONE vibrate, PAUSE, 2 vibrate on a black screen forever. The advantage of having successfully flashed a 9000M ROM allows me to have access to my DOWNLOAD MODE 3 button method, but ever since I flashed that 2.2 i9000 XXJP2 (seems its a euro version) off a torrent I found on the web (When I was desperate to find a functioning 2.2 working version) it seems as though it doesn'T want to boot with any other rom than that one, because all the 9000M roms that I've tried so far flash correctly, and the logo actually changed from i9000 to i9000M on the startup, but they just don't boot.. what could be missing it doesn't seem to be much???
Thanks Mat

If any of this can help, the device was rooted, I was following the darky's mod i9000M guide so I had previously installed the CLOCKWORK MOD and that's as far as I got because my eyes caught the FIRMWARE TOUCH KEY UPDATE which ruined my keys.
Could any of this have screwed something that stops my other roms from booting?
Thanks guys I really want to get this phone up and working again as I don't have much money and am afraid I'll have to cancel with my phone company if I just can'T get this running. I am also willing to make a significant donation to whoever can help me.

You in Canada right? Where abouts?
Sent from my GT-I9000 using xda premium

Quebec province

Alright, if this can help anybody my whole problme is solved.
I flashed the ****JL2**** the KC1 did not boot, the JL2 did.
Once inside JL2, I was able to update my TOUCH KEY FIRMWARE *#*#2663#*#* and everything went back to normal
I have no idea why the KC1 does not work, bugs me out.