Reviving my Galaxy S i9000

Zonda999

Hi guys, I would greatly appreciate it if anyone can help me out here. Basically, when my beloved Neus 4 broke a few weeks ago, I went back to my trusted Galaxy S. Unfortunately, my Galaxy S has now decided to give trouble leaving me smartphone-less!. I don;t think its bricked, at least it shouldn't be. Heres what happened

My Galaxy S had been rooted a out a year ago, from stock Gingergread to CM9, 4.0.3 at the time. The rooting process went fine. However, the other day, the phone shut down sort of randomly as had been happening from time to time. However, it would not reboot. It would not go beyond the loading screen of cyanogenmod.

Thinking that that it may have just been a firmware bug, I decided to have a look around for a solution, I came across this:

http://www.cpkb.org/wiki/Samsung_GT-I9000_Galaxy_S_CyanogenMod_install

I went ahead and performed step two. However, step three did not work and came up as fail on odin. At this point, I tryed starting the phone up thinking that it should launch with the JW5 firmware from step 2. However, the phone will not boot up, it will not go beyond the familiar "S" screen. It just constanlty rebotts itself and the process repeats..

I'm sort of at a loss as to what to do at this point, I don;t think the phone is bricked but then again, I don't know. I thought here would be a good place to ask seeing as a couple of year ago, there was a lot of people round here with Galaxy S's and they were a really popular phone to root and customise at the time

If anyone has any suggestions as to what to do, I'd be really grateful

Banjo String

Zonda999 wrote: »

Hi guys, I would greatly appreciate it if anyone can help me out here. Basically, when my beloved Neus 4 broke a few weeks ago, I went back to my trusted Galaxy S. Unfortunately, my Galaxy S has now decided to give trouble leaving me smartphone-less!. I don;t think its bricked, at least it shouldn't be. Heres what happened

My Galaxy S had been rooted a out a year ago, from stock Gingergread to CM9, 4.0.3 at the time. The rooting process went fine. However, the other day, the phone shut down sort of randomly as had been happening from time to time. However, it would not reboot. It would not go beyond the loading screen of cyanogenmod.

Thinking that that it may have just been a firmware bug, I decided to have a look around for a solution, I came across this:

http://www.cpkb.org/wiki/Samsung_GT-I9000_Galaxy_S_CyanogenMod_install

I went ahead and performed step two. However, step three did not work and came up as fail on odin. At this point, I tryed starting the phone up thinking that it should launch with the JW5 firmware from step 2. However, the phone will not boot up, it will not go beyond the familiar "S" screen. It just constanlty rebotts itself and the process repeats..

I'm sort of at a loss as to what to do at this point, I don;t think the phone is bricked but then again, I don't know. I thought here would be a good place to ask seeing as a couple of year ago, there was a lot of people round here with Galaxy S's and they were a really popular phone to root and customise at the time

If anyone has any suggestions as to what to do, I'd be really grateful

Hi Zonda.

I've had a similar enough problem to yourself, and I really hope your outcome is better than mine.

I was putting new firmware on my phone in order to give it away to my mother who lives in the north, so wanted the phone to be sim-free for her.

All was going well, actually all did go well on odin, I even got the "pass" sign on the programme, only thing is the phone never did boot up, it showed the familiar S sign for a while, then just stuck there.

I turned the phone off, but it wouldnt turn back on again.

I then plugged my usb cable into the phone with the intention of re-flashing the firmware, my laptop made the familair sound it makes upon recognising a device has been connected to it, but the phone never showed up on the laptop.

It wouldnt charge via the wall charger either, so I brought it into fonemenders (I know, I know) who, after a few days tell me the phone was water damaged (it was never next to near water, EVER) and the phone was unfixable.

I refused to take there word for it, and sauntered off to a guy who fixes mobiles in my local town, renowned for being a bit of a whizz kid, who held on to the phone for about a week, then admitted he couldnt fix it, nor did he know what the hell was wrong with it.

I binned the phone shortly afterwards.

Sorry it didnt have a happy ending, but hopefully you'll have a happier outcome than I did.

Zonda999

thanks for the reply

I know its a pretty annoying way to lose a phone. Another thing that annoys me is that the CM rom firmware I was using had been around for ages when I flashed it and it was stable. The thing would seriously put me off rooting an android phone ever again tbh

G1032

Why do you assume rooting the phone has caused this issue?

You might get some help over on XDA. Huge knowledge base there.

http://forum.xda-developers.com/forumdisplay.php?f=656

yoyo

Zonda999 wrote: »

thanks for the reply

I know its a pretty annoying way to lose a phone. Another thing that annoys me is that the CM rom firmware I was using had been around for ages when I flashed it and it was stable. The thing would seriously put me off rooting an android phone ever again tbh

Can you get into the Android recovery (Download Mode)? Battery pull>Re insert it>hold Vol Down, center button and power button simultaneously. If you get the yellow trangle Android logo you can then flash the last official Firmware using Odin, which might be more stable.
I doubt your phone is bricked tbh, I had a Galaxy S also, flashed stock/unofficial many times, no problems.
Also for your computer to detect the phone in download mode, you need the Samsung USB drivers to be installed on the machine (I am fairly certain).
Btw, my experience with the i9000, my custom firmware CM9 upgraded to 10 became unstable. Phone locked up constantly went into deep sleep without waking. Formats/clean installs didn't sort it. A flash to stock ROM then re-flash of CM10 fixed the issue, so I wouldn't rule out the CFW being the cause of the stability issues

Nick

Zonda999

G1032 wrote: »

Why do you assume rooting the phone has caused this issue?

You might get some help over on XDA. Huge knowledge base there.

http://forum.xda-developers.com/forumdisplay.php?f=656

Your right, I don;t know, but the manner in which it shut down randomly the last time I saw it alive and the fact that it never rebooted immediately after that point tells me the software had to have something to do with it.

Basically what happened was I just arrived at work and noticed it had shut down randomly, as it had had done a bit the few days previous. I booted it back up. I was in a hurry and without letting the phone do its media scan and all that, I attempted to make a phone call. I pressed call and at that the screen went blank and the phone appeared to shut right off. At this point ti took the battery out and popped it in again and attempted to reboot the phone but to no avail. I'm not sure what kind of fault it indicates it is but that sort of behaviour hardly indicates a hardware fault?

yoyo wrote: »

Can you get into the Android recovery (Download Mode)? Battery pull>Re insert it>hold Vol Down, center button and power button simultaneously. If you get the yellow trangle Android logo you can then flash the last official Firmware using Odin, which might be more stable.
I doubt your phone is bricked tbh, I had a Galaxy S also, flashed stock/unofficial many times, no problems.
Also for your computer to detect the phone in download mode, you need the Samsung USB drivers to be installed on the machine (I am fairly certain).
Btw, my experience with the i9000, my custom firmware CM9 upgraded to 10 became unstable. Phone locked up constantly went into deep sleep without waking. Formats/clean installs didn't sort it. A flash to stock ROM then re-flash of CM10 fixed the issue, so I wouldn't rule out the CFW being the cause of the stability issues

Nick

Thanks, yeah, I can get into download mode, and recovery mode currenlty. I might try a few recent stock firmwares. Trust me I'd take 2.1 official firmware to get the thing back going again. I might try and flash those later using odin

Zonda999

Good news guys, followed this guide to get 2.3.6 stock firmware back on it and it worked. I think I'll just leave it on that for now until my Nexus 4 is all bandaged up

Actually, getting it back up and running and finally made me do something I;ve been meaning to do for a while, order a new camera lens for it. The current one has gone totally cloudy and this will give it a new lease of life. The part is only a fiver shipped and it should be no bother to fit

natnifnolnacs

I think I ended up with a slim rom on my S1, it was really stable, I gave it to my girlfriend in October and I haven't had to do anything with it since. That'd be my recommendation!