Database Develop

[Q] Phone stuck in reboot loop.

So my brand new 7 day old vibrant is not working now. yesterday i was surfing the droid store, and looking for new apps, and installed a text editor, afterwards i made a text file. and saved it, that's when things went awry, I got a force close message, so i figured no big deal, i'll just reboot the phone. Well after cycling the power, now all i get is the initial splash screen saying samsung galaxy s gt-i9000m and it blanks out, then continues an endless loop. Only way to stop it is to pull the battery. the 3 button combo for force downloading works, but the 3button combo to get the recovery menu doesnt.
Question is can my phone be fixed? is it possible to recover the data ie pics/videos i had on it? or is it borked and i need to take it to exchange it.
Technical information
Virgin Mobile Canada gt-i9000m
Hardware Revision 10.11
running Froyo from box, jp6 i believe was the version.
any help/insight you can offer would be appriciated.
I hope i didnt get one with a bad internal SD card.

i doubt that the app you downloaded had anything to do with it. I hade the same prob. kept rebooting, 3button download mode works. 3 button recovery mode didnt, you need to call bell and get it sent away basically.
out of curiosity, did you do a big file dump onto your phone prior to the dead phone issue? like put on a ton of music or movies or images?
call bell. good luck. i am still waiting for mine.

haha.. don't worry!
just reflash using Odin. for details check this out...
http://androidspin.com/2010/08/09/h...oidSPIN+|+Your+No.1+source+for+Android+news.)

oh yeah, i forgot to mention i tried that too.no go!

SD card fail. You're done.

Your Internal SD Card has failed like many other Bell Phones. Use the Search option to find for possible solutions.

Try downloading a JH2 which includes SBL and flash it (stock 2.1 for your i9000M). I believe you should also check the "Phone Bootloader Update" in Odin.
http://www.multiupload.com/EZF1IEZ34H
If that doesn't work, call it in to Bell and do me a fav and report this failure in the i9000M hardware fail poll. This is the first 10.11 fail I've seen.
Good luck.

Well after searching all over the forums, and finding some similar situations and methods used to correct them.
I've flashed my phone probably 12 times, today and nomatter whatrevision or options i use with odin, it always hangs, in some cases, I'd get past the gt-i9000m black screen, to the galaxy s splash screen, but not past there, i9000ugjh2 seems to get me the furthest along @ the boot screen.
Anyone looking to reflash to a different version, before returning i suggest using the i9000ugjh2 image since it resets the model number to gt-i9000m which, maybe be changed by some of the other firmwares/roms
anyways back to the store tomorrow, since i got snowed in today.
Good luck to anyone else, I will post information on the new hardware tomorrow, If it's 10.11 again i'll have to try and force a failure. But we'll see what we see.

This guy seemed to have been lucky and got is supposed dead I9000m working again. Here's his procedure:
http://forum.xda-developers.com/showthread.php?t=905975
Worth a shot.

update
I received my new handset yesterday, it's another 10.11
I'm going to be treating it with kid gloves for the next few days while I'm at work.
Once I get home I will again begin taxing/loading the internal memory with a large amount of data to test it's stability.
New phone details,
Virgin mobile canada (AKA Bell canada)
Hardware 10.11
Model GT-I9000M
Firmware 2.2
Baseband version I9000UGJL2
Kernel Version 2.6.32.9 - [email protected] #3
Build number FROYO.UGJL2
As for his guide, My previous phone was unable to enter recovery mode, not until i flashed the nutz outta it.
even then his guide was unable to achieve usable results.

i got the same problem , my Phone stuck in reboot loop . its happen when i use some voodoo apps in the market that change the screen i think.
i brought my phone from malaysia.
my Firmware DXJPE.

[Q] Trouble going back to Stock

From what I have gathered... this seems to be a problem that only I have encountered, or at the very least something that I have deemed annoying enough that now I have to solve it... but I recently threw Gingerbread onto my i9000, quite successfully I might add, but I decided I wanted to go back to Froyo until the official release of 2.3 comes out of Samsung, since I am a big fan of "stock".
Problem is, every single ROM (I am at ten and counting) always results in Kies telling me that there is no update available. I have been loading only stock ROMs onto my device, so I am a little confused by this, since even the 2.1 firmwares have given me the same message. I know that, when I had Froyo loaded on stock, the message read that everything was up to date or something along those lines. Having that knowledge just means I won't be able to stop trying to put things back to stock until I see that same message again.
Anyone able to shed some light on what is happening here and how to fix it? Ideally I would love to load up 2.1 Eclair, update to Froyo using Kies and then just call it a day.
(PS. on Gingerbread I am getting some weird "static" screen popping up every time I restart... is that normal? I will take a picture and post it into the Gingerbread review forum if I can capture it.)

i was in a similar boat as you, loading 2.3 was no problem but going back is a pain in the ass.
BE WARNED! I spent nearly a day and i know a fair amount about what im doing, i even had to make the USB jig to force download mode at one point (testing different ideas) so be prepared for some issues.
what i did was use odin to flash stock JL2 (9000M bell version here), with 512 pit and a CSC file from another build (sorry i forget), bootloader update repartition clear efs checked. Thats the ONLY thing i could find to get me back to stock without any internal SD error messages.
IF YOU FLASH THE WRONG THING OR THE FLASHING PROCESS SCREWS UP YOU CAN BRICK YOUR PHONE. Read twice, do once.
See if you can find a stock rom for your area, what your phone came with, with the proper pit file and csc file.
Best of luck, you are not alone. I will definately be waiting for a less buggy leak before i switch back to gingerbread.

Kies reads and looks for the correct software for your product code and firmware tied to the supplying network .Once you install different roms you may change those details and Kies cannot find the correct details on your phone to recognise and match it to a firmware .
Spoof product keys and Kies registry patcher posts may help .
jje

Thanks for the quick answers guys... I shall plug-and-chug a bit more tonight and see if I cannot get something to work... then I will be back to post of my success (or failure).

You can use SpoofFw to trick Kies think you are on an official fw, the let Kies do the stock upgrade for you.

Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?

Wirebrook. I already replied to one of these today. Same happened to me. flashed back to jpu with a view to using kies to upgrade me to jpy but it wouldn't. So flashed eclair jm1 and kies upgraded me to jpy so I suggest that. You'll have to flash bootloader afterwards though as you'll lose 3 button reboot. But don't panic
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 rooted, ADW launcher + gingerbread theme

I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?
Its not an official rom its a Samsung stock rom not the rom that was supplied with your phone . Kies might update it or might not .
You have firmware provided by the original phone seller and product codes hardware id firmware id for that . Kies will see that and update .
But its going to show not the firmware supplied by the original phone seller and tied to product code etc . Then requires you to Spoof Kies for an update .
jje

@Mossy1963
I'll give it a shot this evening... I have the JM1 firmware glaring at me in the face on my desktop right now, though... not sure that worked right the first time.
@JJEgan
As long as it is all "stock" I am pretty much fine with it at the moment. Not too bothered with having it tied to it's specific product code so much, although that would be nice.

wirebook said:
Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has mys product code become screwed up?
Click to expand...
Click to collapse
That error message its actually wrong, you get it because nv_data.bin could not be found in /efs folder.
This could be due to a faulty flash where Csc was not applied correctly in recovery on the first boot.
Reflash with Odin is the solution.
Sent from my GT-I9000 using XDA Premium App

@Mossy1963
No cigar whatsoever... Kies simply stated there was no update to be done. Oh well.
@LuffarJoh
Tried reflashing... didn't work either.
Aaaaand to make things weird, that sometimes-working Antenna suddenly started working with an Eclair ROM that it hadn't worked before. Then after a reboot... nothing anymore. And now I have flashed the thing back to Gingerbread and what do you know... no more antenna. I would much rather have a working phone as opposed to a "perfect-stock" phone, so it looks like I might have to get an exchange... and perhaps acquire what I was after in the first place at the beginning of this thread anyways.

Hi, I was wondering exactly the same thing after flashing 2.3.3 today. I just like the idea of being able to plug the phone into kies to get a proper release although, I've no doubt the exact same version will be available for download. Has anyone got any useful info ?

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.

[Q] "Unknown volume for path" - can't get Download screen

I attempted to restore a backup via CWM and now I get the message E: unknown volume for path" in response to any options in CWM. If I try to reboot normally, I just get the SGS splash screen, which just stays there.
I can't get to the Download screen with the three keys, this just gets me back to CWM. So I feel pretty screwed now. I could order a jig but will it even work in these circumstances?
The sequence of events that led to this was that I followed the instructions here to install Jellybean 4.2. All went well, Jellybean was running very smoothly from this rom. The trouble was that I just couldn't get it to find any mobile networks at all, even when I manually entered the APN and VPN etc. My sim is a giffgaff one, which uses the O2 network, and you do have to add the APN to get the 3g to work - but the phone just wasn't seeing any networks at all. I presume this was because this version of the rom just doesn't recognise UK carriers.
So anyway, I then went into CWM to restore my last backup, which was from over a year ago. This all appeared to work but then it got as far as the SGS splash screen, as described above, and stayed there.
What else can I try?

Well, I did manage to get a Download screen in the end, although Odin running on my Win 8 desktop couldn't see the phone. However, I then put Odin on my netbook running Win XP and that can see it.
So I'm now ready to flash a stock rom to the phone. I've tried following PuggeredUK's guide to installing a stock rom, which I've used successfully in the past, but he does say you need a .pit file. I've tried loading a stock 2.3.4 and 2.3.6 value (which was the last stock firmware I had on the phone) roms from Sammobile but can't find any .pit files in any of the stock roms I've downloaded from there.
So are .pit files actually necessary? I tried sending one file to the phone and Odin said "Failed", so I thought I'd better check about the .pit files before further buggering up my phone.

I had this same problem too when I restored my backup. I got it fixed by just going back to the ROM what I had before I tried to restore. (which was CM10).

Do what I just told this guy in post #7
http://forum.xda-developers.com/showthread.php?p=38194645
Edit: and you lost your network because you flashed from GB to JB, missing out ICS. Nothing to do with the rom and uk carriers. Next time install ICS first.
Sent from my GT-I9000 using Tapatalk 2