[Q] Galaxy S reboots by itselft, NO SOLUTION FOUND - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
I have bought a Samsung Galaxy GT-I9000 six months ago. It always restarts by himself or crashes. And I've still couldn't find the problem. I have already tested with: Gingerbread 2.3.5, 2.3.6 and Cyanogen 7.1 and 7.2 RC1. What happens is that with Gingerbread it restarts autmatically while on the Cyanogen it only crashes and I need to remove the battery and reinsert it.
I've taken my phone to a Samsung technician. He said that my battery was with 90% of its capacity, the memory and processor were tested and they are ok. He said that it wasn't any hardware problem.
His conclusion was that Android wasn't a good OS, and that is happens with all phones. But if the hardware is OK, and I've hard resetted many times, installed a lot of differents OS, why does the problem still persists? It just doesn't make any sense.
The interesting part is that when the phone has few application, the phone works fine. It only start restarting when I install 10 applications from market, for instance.If I have 3 apps installed, it may reboot but much less frequently.
In your opinion, was the conclusion of the technician correct?

I've encountered similar problem a long time ago. At that time I deleted the apps , and then rebooted the phone, one by one and finally the SGS works fine again without a certain app. So try to find out which app crashed your phone.

App is not responsable for the reboot
Well, I don't think this issue is related to a specific application. Because the technician also noticed the problem when he installed a lot of applications that he has chosen without knowing my apps.
Besides that I am using the common ones like: Facebook, WhatsApp, YouTube, Gmail, Google Maps, Skype, and BBC News. They are all updated. I don't think any of them has a bug that resets the phone.

My Phone will reboot by itself sometimes when i enable wifi
This has only started since Darky's 10.2 (JVQ kernel) has been installed on my phone. I have since installed ICSSGS 4.2 with semaphore 0.91 (no reboots) and are now back on stock (factory/carrier) gingerbread ROM and rebooting occurs when wifi is enabled sometimes.

Try cm9. I used to get random reboots on gingerbread roms but since being on cm9 I haven't had one. Current using the latest nightly with stock kernel and have been running since build 7. Battery life is great and is stable. I highly recommend :thumbup:
Sent from my I9000 running CM9

Something is dodgy, imho, backup all apps using Titanium, wipe phone, wipe caches, factory reset, then install stock gb, say jw4 using odin with pit file and repartition, hard reset again, then root using latest semaphore kernel. Remove usual bloatware, then Restore apps 1 by 1 to see what's causing the problem. Think its always best to start from scratch. Backup efs folder, and sms etc first.
Sent using TCP/IP

More info
Wait guys, you are using the terms I don't know.
About the comment: "then install stock gb, say jw4 using odin with pit file and repartition, hard reset again, then root using latest semaphore kernel. ", I have some questions:
What's stock gb? What is jw4? Can you send me a link about how to do so or where I can download jw4? There is semaphore kernel and stock kernel? What is the difference between them? The original kernel is not good? Why do I need to install it?
The other commend was: "Current using the latest nightly with stock kernel". I will try that. But how can I install cm9 with stock kernel? Could you send me a link with the steps?
About the comment: "I have since installed ICSSGS 4.2 with semaphore 0.91 (no reboots) and are now back on stock (factory/carrier)". Never used Ice Cream Sandwich for Samsung Galaxy S. How can I install it with semaphore 0.91? Is this OS better than Gingerbread and Cyanogen?
Sorry about the stupid questions,

Related

Constant rebooting

i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.

[Q] How to use ROM Managar - Please Help

Hi,
I've just downloaded ROM Manager free from Market.
I need to update to froyo without connecting to PC (I don't have UPS and power shut downs are common in my area. Moreover, installing from phone seems to be simple).
I've clicked Flash to Clockwork Mod Recovery. And Have backedup Current ROM.
How do i update now?
I have downloaded a XXJPU firmware from sam-firmware.com
It consists of the following files
GT-I9000-CSC-MULTI-OXAJPU.tar.md5
I9000XXJPU-REV03-PDA-low-CL747761.tar.md5
MODEM_I9000XXJPU.tar.md5
s1_odin_20100512.pit
Are these files enough to update through ROM Manager? If yes, where should i place these files and how do i proceed?
Please help - have been in stock firmware since I've bought. (No Froyo nor gingerbread, because of my lack of knowledge )
Thanks in advance!
The files which you have mentioned can only be updated through Odin or Heimdall which requires computer access.
The only way which I know that you can flash through ClockworkMod recovery is through custom firmwares. Bear in mind that the custom firmware which I'll be providing the link to is Froyo (2.2.1)
http://forum.xda-developers.com/showthread.php?t=814091
Follow the "Clean guide" which shows how to install that custom firmware with the highest percentage of success.
(JUST follow step 4, the part where you need to transfer the custom ROM into your phone and NOT the part about CWM "update .zip" since you already have clockworkmod recovery)
And then, jump/skip all the way to step 12 and follow the procedures from there normally.
I assume that you have a clean eclair ROM which does not have any tweaks/lagfixs (such as Voodoo etc.)
Hope this helps.
Thanks man.
I'm really afraid of using custom ROMs...
If only there was an easy way to update to official ROMs...
Anyway, i'm going to try this Darky's ROM. Hope it is not filled of bugs.
Installed Darky's ROM. Thank you and Darky. I finally got froyo.
ROM Seems to be super fast. But lags(gets stuck in some apps) more frequent than eclair
And seems to have bugs
Like for example: Defauly Music Player is not working properly.
Also lost default Galaxy S lockscreen (though i can get than using an android market app)
Not sure about battery though.
Problem solved. Will be replying in Darky's thread about the bugs...
emmarbee said:
Installed Darky's ROM. Thank you and Darky. I finally got froyo.
ROM Seems to be super fast. But lags(gets stuck in some apps) more frequent than eclair
And seems to have bugs
Like for example: Defauly Music Player is not working properly.
Also lost default Galaxy S lockscreen (though i can get than using an android market app)
Not sure about battery though.
Problem solved. Will be replying in Darky's thread about the bugs...
Click to expand...
Click to collapse
When you go from eclair to froyo, a factory reset is a must otherwise you will stuck with force closes and crashing apps, make sure you back up your apps, contacts and text messages then preform a factory reset after that your sgs will run fast and smooth buddy.
Then there is this battery issue, with costum rom your battery will drain quicker, so do a full charge then reboot into recovery and search for battery stats and do a battery wipe, this will add some more power to your battery.
Sent from my GT-I9000 using Tapatalk
emmarbee said:
Installed Darky's ROM. Thank you and Darky. I finally got froyo.
ROM Seems to be super fast. But lags(gets stuck in some apps) more frequent than eclair
And seems to have bugs
Like for example: Defauly Music Player is not working properly.
Also lost default Galaxy S lockscreen (though i can get than using an android market app)
Not sure about battery though.
Problem solved. Will be replying in Darky's thread about the bugs...
Click to expand...
Click to collapse
There's a version 6.0 from Darky
http://forum.xda-developers.com/showthread.php?t=814091
Follow the steps from the new "Installation guide" and remember to do step 7 if you think that your phone is not performing up to par.
Make sure to back up your stuff onto your internal or external SD-card before proceeding and follow ALL the steps shown there

[Q] "Application is not installed on your phone" Error

Hi all,
I've done a search on this (both XDA-wide, and Google) and no-one seems to have a valid answer for me yet.
I am running Gingerbread (PDA = XWJVB, Phone = XXJVK, CSC = XAJVK) via a Doc's beta RomKitchen build. I am aware that I am running a beta and things can get a bit hairy, but this problem is really annoying.
Basically after the rom flash, I went and got Titanium Backup working again, and started restoring my favourite apps and widgets. All worked fine, then I had to do a reboot for some reason. All the restored apps are still in the apps folder , but greyed out and with an SD-card image overlaid to tell me they are on the SDCard. They ALL no longer work but give the "application is not installed on your phone" error, which is annoying, because before the reboot, they all worked.
I have tried twice to restore them from Titanium backup, and each time they only work until the next reboot breaks them, meaning the only apps I get to keep are the system apps and the ones I cooked into the Rom.
Anyone have any ideas?
Anyone at all?
Hi, I had a similar problem, with one difference: it started after a while. I had Doc's JVK installed, I restored my apps with Titanium Backup and it worked flawlessly for a while. At some point I noticed that the apps installed recently would disappear after a reboot. The worst thing is that even the market disappeared at some point.
To solve the problem, I flashed several times a WIPE version of Doc's rom along with several wipes from recovery. It didn't work right away and it took me several reflashes.
No problems since then.
Cheers
Thanks for that.
After much reading, I reckoned it was probably the Fugu kernel doing most of the damage, so I flashed a Chainfire XWJVB kernel, then a recooked Doc rom without the Fugu kernel. Lubberly Jubberly now

[Q] Abnormally Slow Galaxy S Captivate - Factory Reset Doesn't Help

Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5. I have rooted my phone with Odin3 v 1.85, but it's been running slow even before the root. (In fact, I rooted the phone so I could install a lagfix, but I can't find one for Captivate I897 running on 2.3.5).
Anyway, I don't see the reason for games and apps to be running slow because I've heard that the Captivate has a pretty good GPU. Also, it's not like I've overstocked my phone's storage; I only have a few apps.
I've also made a short video explaining my problem further. Just search "slow captivate" on youtube. I should be the first video: "Really Slow Samsung Galaxy S Captivate - Fix?"
I've searched everywhere for a fix, but I can't find anything, so I came here. Does anyone have an idea on how to fix this, or at least reduce the lag?
Thanks in advance,
-xxTDGPainxx
I was seeing my phone work slower and slower on 2.3.6, I suspected that the developers of the apps I used were starting to develop for ICS and that maybe it was different enough that the updates were causing the apps to misbehave on older versions. I flashed to ICS just to see... and it was a great move, ICS on the captivate flies!!! I used SlimICS, I think it is the right way to go for Galaxy S phones...
xxTDGPainxx said:
Hi, first of all, I am new to Android devices.
I am having a problem with my AT&T Samsung Galaxy S Captivate. Games and apps seems to be running slower than normal after updating to Gingerbread 2.3.5.
Click to expand...
Click to collapse
Have you run any tools to see what is sucking up your phone's resources?
[email protected] said:
Have you run any tools to see what is sucking up your phone's resources?
Click to expand...
Click to collapse
No, I don't think I've checked that. What app do you recommend on checking that?
xxTDGPainxx said:
No, I don't think I've checked that. What app do you recommend on checking that?
Click to expand...
Click to collapse
I would say cpu spy
Sent from my SGH-I897 using xda premium
First of all, lagfix isn't really used anymore. Also, I would say to get rid of those task killing apps. They don't help and only add to your problems. A lot of the symptoms you encountered are pretty common, and I was expecting something much worse. You seem to be running a different kernel that allows overclock; which is it?
If all else fails, try ICS
Sent from my ICS Samsung Captivate
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
xxTDGPainxx said:
Hey
I tried to upgrade to ICS with Team ICSSGS [Android 4.0.3]. I followed a step by step tutorial using CWM to load "ICS_4.0.3_MR1-RC4.2_Captivate.zip" and installation seems to go well. But after I try to reboot my phone, the AT&T logo comes up, then the "Google" logo comes up, but it just stays stuck at the Google logo forever. ICS never starts up. I've tried removing the battery and then going back into CWM and restarting the process but the same thing keeps happening. What should I do?
Click to expand...
Click to collapse
You flashed it twice, correct? Try wiping your data.
korockinout13 said:
You flashed it twice, correct? Try wiping your data.
Click to expand...
Click to collapse
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
xxTDGPainxx said:
Yeah, I've flashed it a few times. Each time, before I install it, I clear data/factory reset, clear cache, and davlik cache, but it's still just getting stuck at the "Google" boot screen. It's weird because every time, CWM says it installs successfully. I'm starting to think that the .zip I downloaded isn't so good...
Do you know of a good, stable version of ICS I could use instead? Maybe even the same one you're using?
Thanks
Click to expand...
Click to collapse
This is the stable ics in my opinion, but i use aokp by sixstrings.... http://forum.xda-developers.com/showthread.php?t=1362092
Sent from my SGH-I897 using xda premium
Maybe don't wipe dalvik cache. That can sometimes result in that happening
Sent from my ICS Samsung Captivate
I gave up on ICS... I could not get it to work for the life of me and it was getting me extremely frustrated. I almost bricked my phone (I think).
Maybe I'll try it again if someone could link me to a detailed step-by-step tutorial to upgrading to ICS. I'm very new to the way android works and a lot of the tutorials are just plain confusing to me...
I ended up reverting back to GB 2.3.4.
Thanks for helping me out though.
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
korockinout13 said:
Try reading some stickies, there are some great guides. There's also one in my sig.
Sent from my ICS Samsung Captivate
Click to expand...
Click to collapse
The one in your sig is about the best I've seen. Great job!
GUIDE TO INSTALL ICS, my way at least
Hey if you're looking for a good guide to putting ICS on your captivate I can help, The first time i tried ICS i messed things up and angrily decided that i wouldn't try it again and reverted back to 2.3.5, after carefully trying ICS again i love it so much. I won't ever go back to android 2.whatever.
I used CM9 ICS and have no issues or bugs. It's possible there are other better ICS roms but i prefer this one since i know for a fact that it works great.
http://forum.xda-developers.com/showthread.php?t=1363760
You'll need to download CM9 v17 and a gapps package on your SD card.
trust me, ICS is worth it, it's much better than 2.3
if you have titanium backup backup your user apps (NOT SYSTEM APPS/SYSTEM DATA)
Rom installation:
First things first always do a nandroid backup so you can go back easier, if necessary.
once thats done go to CWM recovery and do a wipe data/factory reset, wipe cache partition. once that's done install the CM9 .zip package for the rom.
IT WILL STOP HALFWAY THROUGH AND REBOOT ITSELF, as this is the new kernel being installed. while it's still rebooting pull the battery and let it turn off, reboot straight into CWM recovery.
once this happens go back to install you CM9 .zip file again. it will finish all the installation after that. once it finishes the install you should definitely install the Gapps.zip. it will load up your google apps (market,gmail,youtube,etc and your google account sync) if you don't load the Gapps you will not have very much functionality to your captivate.
once you have your google apps installed you should be ready to fly with a fast responsive captivate. Hope this helps, it took a few trial and error runs before i figured it out.
If you used titanium backup to backup your apps you can restore APPS ONLY!!! don't restore any system data/system apps!!!! it's very important that you don't do that.
that should be it. enjoy your ICS, it's much better than android 2.blah
Fastness: CM7
Sexyness: CM9
That's the answer to everything.
I have run aokp (my current) and doc's master. Both have been great!
I'm far from an Android guru but if you follow the directions, you will be ok. Both also have relatively supportive forums if you get in a jam.
Sent from my SGH-I897 using Tapatalk

[Q] Sorry folks - this is probably a dumb question

Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
nickpb said:
Firmware: 2.2
Click to expand...
Click to collapse
It would be simpler just to connect it to KIES and let it update your ROM according to its specs without any worries, If it fails than you can chose latest ROM from here its based on region, so chose latest for your region
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
nickpb said:
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
Click to expand...
Click to collapse
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
AlwaysDroid said:
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
Click to expand...
Click to collapse
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Hi.
I think if u be in GB ROMs , it's better , then go to new bases like ICS or JB slowly.
Hey I recommend you just to update it via Kies. You will probably get 2.3.6 GB Value Pack. Its pretty good, and stable, atleast for me. If you are not satisfied with preformace that you get with it, you can install custom kernel, such as semaphore, so it would get better,
If you lived with froyo till now, you wont need anything more than GB. And you can be sure about stability, good signal, no restarts and so on, that you can get on some custom ICS and JB roms...
snapper.fishes said:
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Sent from my GT-I9000 using xda premium
AlwaysDroid said:
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Click to expand...
Click to collapse
Please don't be misleading. CM10 is certainly good in it's own right, but there are quite a few things that are not working.
For instance, Google+ instant upload is completely non-functional because of an incomplete implementation in both the camera and gallery apps. This is clearly a rom problem.
The gallery app also has no settings. There is a menu option to access settings, and one would expect to see a settings screen similar to the one in CM9 when that settings menu is clicked. Instead the user is greeted with a blank screen.
Users need to be fully aware of what they are getting when choosing a rom and making statements like "it is almost perfect" is subjective and can be misleading.
Finally you say that CM10 has "almost no bugs" and then follow it with "... nothing" which is an obvious contradiction. Which is it, almost none, or absolutely none?

Categories

Resources