I'm facing a problem very similar to the one described in this thread.
As one can see in the picture, the screen gets all blue.
After trying so many things, I came to the conclusion it's NOT a hardware problem because if I go back to stock GB, the screen is fine.
It's also fine if i install ICS, with CWM 5.x.
On the other hand, if I go to any JB ROM, tryied many ROM's and several kernels (mackay, semaphore, devil, ...), all of them brings the same blue screen.
To me, it seems to be a problem with CWM version 6 or above. Which is kind of strange, because I couldn't find anyone else having the same problem, except for the thread above.
So my questions are:
1) is there a way to have JB, but keep stock recovery instead of CWM? Or maybe have JB 4.3 with CWM 5.x ?
2) maybe there's a place where CWM keeps its settings and I can go there to delete them and/or reset them?
Some history:
I managed to install JB 4.2.2 and it was working for over 1 month. One night my wife installed an app called Jater Calendar and started playing with its color settings. The battery went dry and the next morning the phone booted up all blue.
I've already tried to install that app again and try to find some "restore settings", but I couldn't find anything.
Maybe it's just a coincidence, some app shouldn't change CWM settings like that. Or could it?
MrCabana said:
I'm facing a problem very similar to the one described in this thread.
As one can see in the picture, the screen gets all blue.
After trying so many things, I came to the conclusion it's NOT a hardware problem because if I go back to stock GB, the screen is fine.
It's also fine if i install ICS, with CWM 5.x.
On the other hand, if I go to any JB ROM, tryied many ROM's and several kernels (mackay, semaphore, devil, ...), all of them brings the same blue screen.
To me, it seems to be a problem with CWM version 6 or above. Which is kind of strange, because I couldn't find anyone else having the same problem, except for the thread above.
So my questions are:
1) is there a way to have JB, but keep stock recovery instead of CWM? Or maybe have JB 4.3 with CWM 5.x ?
2) maybe there's a place where CWM keeps its settings and I can go there to delete them and/or reset them?
Some history:
I managed to install JB 4.2.2 and it was working for over 1 month. One night my wife installed an app called Jater Calendar and started playing with its color settings. The battery went dry and the next morning the phone booted up all blue.
I've already tried to install that app again and try to find some "restore settings", but I couldn't find anything.
Maybe it's just a coincidence, some app shouldn't change CWM settings like that. Or could it?
Click to expand...
Click to collapse
Just to clarify some of your questions:
-CWM 5.x.x.x is only compatible with Gingerbread and ICS. JB can only use CWM 6.x.x.x (as far as I've see for the S anyway). So no, you can't use CWM5 on Jelly Bean...
-I don't think CWM has this setting in recovery. Other kernels such as Semaphore with its own custom recovery might.
I took a look at the other thread and what xsenman and you posted, and this SEEMS like a hardware fault but isn't... I mean if colour corrections apps + advanced device settings don't work, then this is usually beyond the software.
Which version of Mackay have you tried- stock CM colours or Voodoo? Or have you tried both?
EDIT: Hold on a moment. You have an I9000B...
I9000B roms are NOT the same as the international I9000.
Hmmm.
Try Helly Bean- and make sure you get the I9000B version- and see if that changes anything. Or you could try CM builds for the I9000B (the code for it is galaxysbmtd).
I don't think its very likely but it MAY be due to the device (and therefore the kernels, even if they're only miniscule) being different.
Sent from my GT-P7510 using Tapatalk HD
Thank you very much for your quick response.
"this SEEMS like a hardware fault but isn't"
It can't be! If hardware were faulty, it wouldn't work on ICS or GB.
"Which version of Mackay have you tried- stock CM colours or Voodoo? Or have you tried both?"
Both, 0.199 Final CMC and VC. Also tried Devil3 (CMC and VC), GearKernel (JB, JB3, JBPlus) and Semaphore JB 2.9.12b.
All of them load the logo fine for 1 second, then it flashes really fast and becomes blue.
I'm wondering whether its to do with the fact that you flashed roms that weren't meant for the I9000B.
Try flash this- make sure you download the I9000B version- and see if the results are the same: http://forum.xda-developers.com/showthread.php?t=2012061
Sent from my GT-P7510 using Tapatalk HD
Yes, I know that ... the versions of CM I am using are all for i9000B. I even tried the i9000 (without B) to see what happened. It's also blue and the touch doesn't work.
I also tried Helly Bean (the 4.1.1 or 4.2.2 version, I don't remember which), same blue effect.
MrCabana said:
Yes, I know that ... the versions of CM I am using are all for i9000B. I even tried the i9000 (without B) to see what happened. It's also blue and the touch doesn't work.
I also tried Helly Bean (the 4.1.1 or 4.2.2 version, I don't remember which), same blue effect.
Click to expand...
Click to collapse
Hmmm.
If you're on 4.2.2... Have you tried this as well? (sorry, I know I'm probably not helping too much but its better to try everything and see if SOMETHING happens I guess)
http://forum.xda-developers.com/showthread.php?t=2105611
Sent from my GT-P7510 using Tapatalk HD
Yes, I had tried this one. It's the same file I downloaded yesterday.
The results are the same.
MrCabana said:
Yes, I had tried this one. It's the same file I downloaded yesterday.
The results are the same.
Click to expand...
Click to collapse
Damn. Then I'm sorry, I really have no idea what's going on :/
The only thing I can think of is to ask your wife what exactly she did before that happened using that app...
Or (I'm not sure whether this is possible so someone else may have to correct me) somehow grab a logcat. I'm not experienced with logcats so I can't help you here: but there may be a possibility that taking a logcat, especially during booting (because you mentioned something like it being normal for one or two seconds before going blue) might reveal something, but as I said, I really don't know...
Try PM a developer you can get in touch with and see if they can do anything about it.... Or alternatively (if you ahven't already) try post in the CM thread and pawitp might know something.
Sent from my GT-P7510 using Tapatalk HD
This blue screen problem is very common
Hi
It seems that this blue screen problem is very common in this forum.
Did someone manage to solve this problem, or is familiar with a working solution?
Just in order to be organized and help others, here is a reference to some of the users and their posts regarding this problem:
MrCabana in [Q] Samsung Galaxy S i9000B blue screen problem
kssthomas in [Q] Samsung Galaxy S blue screen error, which also posted a video in YouTube - Samsung Galaxy S i9000 - Blue Screen problem
IntelVN in [Q] [PROBLEM] Blue Screen On GT-I9000
The only thing that I got from all of these threads is that it's probably because of CWM 6.x and above, and that in CWM 5.x everything is okay. (Thanks a lot to MrCabana for this conclusions)
So, did someone manage to solve this problem, or is familiar with a working solution?
Edit: I posted a thread in which I summarize all I know about this issue.
Edit: This issue is solved. Please look in my thread for more information.
need4steer said:
Sorry, I never found a solution to this problem.
Ended up buying another digitizer and after that, it started working again with CWM 6.0 and above.
Even though the problem seems to be "solved", I refuse to accept that as a hardware problem since (again) it was working fine with CWM < 6.0 even with the (maybe) broken screen.
Click to expand...
Click to collapse
MrCabana said:
need4steer said:
Sorry, I never found a solution to this problem.
Ended up buying another digitizer and after that, it started working again with CWM 6.0 and above.
Even though the problem seems to be "solved", I refuse to accept that as a hardware problem since (again) it was working fine with CWM < 6.0 even with the (maybe) broken screen.
Click to expand...
Click to collapse
Really?
Will you please describe in details the steps you did in order to solve this problem?
Edit: I posted a thread in which I summarize all I know about this issue.
Edit: This issue is solved. Please look in my thread for more information.
Click to expand...
Click to collapse
There are no steps. I just replaced the screen digitizer.
MrCabana said:
There are no steps. I just replaced the screen digitizer.
Click to expand...
Click to collapse
Well, thank you for letting us know.
So weird that your screen was fine with CWM 5.x and ICS, and bad and bluish with CWM 6.x and JB, and still a hardware replacement solved it.
What caused you to finally replace it although it doesn't seemed as a hardware problem?
How did you know to replace this specific part?
Edit: I posted a thread in which I summarize all I know about this issue.
Edit: This issue is solved. Please look in my thread for more information.
Related
Hi!
Im having trouble getting into CWM. I have been running MIUI on my Galaxy S i9000 for over a month now without any problems with CWM. Im running MIUI RC8vC right now and decided to update it to the latest release MGv2, but here comes the problem. I can't get into the Clockwork Mod Recovery mode.
What i have been trying is the standard 3-button-combination, where i end up on the splash screen for the Galaxy S i9000 and than nothing more happens (left it on for 10 minutes just to be sure). So i then tried rebooting into CWM using the ROM Manager from Market, ending up with the same result.
My question is, what is the most simple way of fixing this annoying problem?
Thanks!
how long are you holding the 3 button combo for ? you only need to do it until the GT-I9000 screen comes on, then let go.
anyway if you cant get it working its probably kernel related, did you flash they CM7 initial kernel before you came to MIUI,
do this again in ODIN and start the process again
Yepp that's what im doing, I have been using CWM quite a lot so im 100% sure im doing the combo correct, it seems like the CWM just wont boot up.
Yes i did, and after that i have been upgrading MIUI like 10 times for every new version without any problems at all, up until now with this release.
So the solution is to Flash the initial kernel again, then use the 3 button combo and install the latest release and all will be fine again hopefully?
RobertRoos_ said:
Yepp that's what im doing, I have been using CWM quite a lot so im 100% sure im doing the combo correct, it seems like the CWM just wont boot up.
Yes i did, and after that i have been upgrading MIUI like 10 times for every new version without any problems at all, up until now with this release.
So the solution is to Flash the initial kernel again, then use the 3 button combo and install the latest release and all will be fine again hopefully?
Click to expand...
Click to collapse
yes, that should work
weird problem and i have never heard of it before lol..
Thanks for the quick answer!
I did what you said and it worked fine, im now running the latest release of MIUI for Galaxy S.
But now i can't get into CWM again! This is really strange, and annoying, if i have to go back to the initial kernel all the time for upgrading MIUI, i do wonder what could be causing this problem. If it was the kernel that comes with the later releases av MIUI i suppose others would have similar problems, but i can't find anyone else having these kinds of problems.
Seems like im beeing followed by bad luck today.
so download mode IS working ??? Hmmm.... not a 3 button combo issue then..
How long have you been on MIUI, did you come from a gingerbread ROM ?
can i just ask how are you doing the 3 button combo..... (i feel stupid asking this, but this problem is so strange)
Yes, works like a charm- so as I said im on the MGv2 right now but with the same problem as before lol.
I've been on MIUI for about a month now, perhaps a little longer. No i came from Darkys v9.5, than did the standard update procedure going to a stock froyo rom and so on as described in the main MIUI thread.
Well im doing it the same way both when on the kernel for CM7 where i can get in, and when on the kernel for MGv2. Menu+Volume Up+POWER, Releasing Power directly when the "Galaxy S i9000 Samsung" splash screen turns up. So im 100% im doing the combination right. I can't get into CWM using the ROM Manager either that donät require the 3-button combination, so there must be something else.
Thanks for trying to help me with this!
no need for thanks we havent got it sorted yet lol
make a post in the MIUI thread in development, there is a lot of cleverer people in there and im hoping that they can shed some light on this bizzare situation
I wanted to do that in the first place, however i must reach 10 posts or so before i can post in there. You could not post my question in there for me you think? So i don't hace to just spam this forum with another 5 posts.
thats very respectful of you not wanting to spam the thread, but yes i will post your question now for you,
you can keep your eye on the post and watch the results, i will also post the results here when someone kindly answers it
EDIT: have you done a factory reset ? when in recovery did you format /system /cache / dalvik cache and then install MIUI
hey mate had a reply, dont know if you have been checking but here is what was said
I had a similar problem when first installing CM7, I believe it is a problem with having come from the original JVK. The solution was to flash an older Froyo version (JS3 in my case) and repartitioning with 512-pit, then installing MIUI again from scratch. Hope that helps.
Click to expand...
Click to collapse
hope this helps
Ill reply when more solutions come up
azzledazzle said:
thats very respectful of you not wanting to spam the thread, but yes i will post your question now for you,
you can keep your eye on the post and watch the results, i will also post the results here when someone kindly answers it
EDIT: have you done a factory reset ? when in recovery did you format /system /cache / dalvik cache and then install MIUI
Click to expand...
Click to collapse
azzledazzle said:
hey mate had a reply, dont know if you have been checking but here is what was said
hope this helps
Ill reply when more solutions come up
Click to expand...
Click to collapse
Thanks again azzledazzle!
Yes a did a complete wipe since I as well thought that might could solve the problem, however it did not.
Okay I will have a go at it tomorrow- I guess i need to find a ROM with a bootloader and all though when downgrading from 2.3.4?
yes, im not sure which firmware contains the bootloader or if you have to check 'update bootloader' in odin, i have never had to do this, so you will have to search.
but let me know how you get on and we can go from there.
Im off to bed now its late, if you get it fixed PM me, if not il be back to check on the thread tomo
Problem is now solved!
I was thinking that MIUI gets updates all the time, and switches between kernels quite often as well, so I decided to wait for the next update with a kernel-switch.
MGv4 was released today and had the kernel-switch I had been waiting for, so I just flashed over the initial kernel for CM7 again using ODIN. Than went into CWM and updated MIUI to MGv4.
Than with my fingers crossed i tried entering CWM again and it worked like a charm.
So I did not have to go back to FroYo and all that again, just had to wait for the next update.
Thanks for your help!
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..
pvtjoker42 said:
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..
Click to expand...
Click to collapse
Hi there, thanks for reply back to me.
I've managed to actually get it going again, by reflashing to the Overcome kernel.
However, some apps has disappeared and also the market.
Anyways, i wish to revert the whole thing back to stock, kernel and firmware. Is there a way I can do this via Kies?
Let me know what information regarding my tab you need. I believe it is the CPW (GSM) UK version.
cheers
geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).
LOL, +100000000000000000000000 thepitbull...
thepittbull said:
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).
Click to expand...
Click to collapse
Hi there,
Thank you so much for your time in replying - I've managed to install what i believe is stock Gingerbread from Samsfirmware. So everything looks back to normal... tho i have posted another Question, with all my firmware details so I can be reassured I am back to stock.
So sorry, I panicked so badly last night..ha!
You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.
nidza said:
You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.
Click to expand...
Click to collapse
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk
k0sh said:
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App
geoyakult said:
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
best reaction i never read
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl
I am now using the Original Stock ROM and downloaded several Apps. After few days, it just gave me headache because of rebooting issues.
I downloaded already the following files:
CWM 5.0.7
Titanium Backups
BusyBox
SuperUser
But still, I encountered rebooting problem.
Can somebody help me?
If this one solve, then, I will add the solution to my Official Thread.
Thanks in advance Guys.
im on v20m stock rom...rooted but havent flash any clockwork recovery...so far havent got any reboot and in fact its the most stable ROM i use so far(from v20f stock to cm7 to cm9 to v20j stock to v20m stock)
what stock version do you have?
you said it started after downloading certain apps...try uninstalling those then check if it will still reboot.
last i would recommend is smartflash the stock rom again
In my experience, I've had random reboots for a number of different reasons. It's hard to tell what may be the cause just based on your description. Please provide more details. For example, Does it boot at all and then reboot after some use? Or are you stuck at the boot animation and cannot go to the home screen at all?
And when you said you are on stock ROM, is it the same stock you had before? Or is it a different one?
To share some of the reasons I've had in the past...
1) Incompatible kernel (may not be your problem since you are on stock)
2) Overheating (usually due to overclocking too rigorously and/or wall charging)
3) Messing up with settings somewhere
And as chupi said, just basing on what you wrote, it may be related to one or a combination of the apps you installed. Or, there may be just a bad combination of the apps that you are using.
I hope you have a backup prior to the app installation. That should help narrow down things, or at least go back to the pre-problem stage.
chupi_24 said:
im on v20m stock rom...rooted but havent flash any clockwork recovery...so far havent got any reboot and in fact its the most stable ROM i use so far(from v20f stock to cm7 to cm9 to v20j stock to v20m stock)
what stock version do you have?
you said it started after downloading certain apps...try uninstalling those then check if it will still reboot.
last i would recommend is smartflash the stock rom again
Click to expand...
Click to collapse
Thanks Chupi.
It is Okay now. I think, it is because of Fruit Ninja, Half Brick application. So, I just uninstalled it.
Also, I disable Background Apps of Yahoo Mail.
Everything is now OK.
I am using V20M.
Regards,
Jose Rey
aragorn7 said:
In my experience, I've had random reboots for a number of different reasons. It's hard to tell what may be the cause just based on your description. Please provide more details. For example, Does it boot at all and then reboot after some use? Or are you stuck at the boot animation and cannot go to the home screen at all?
And when you said you are on stock ROM, is it the same stock you had before? Or is it a different one?
To share some of the reasons I've had in the past...
1) Incompatible kernel (may not be your problem since you are on stock)
2) Overheating (usually due to overclocking too rigorously and/or wall charging)
3) Messing up with settings somewhere
And as chupi said, just basing on what you wrote, it may be related to one or a combination of the apps you installed. Or, there may be just a bad combination of the apps that you are using.
I hope you have a backup prior to the app installation. That should help narrow down things, or at least go back to the pre-problem stage.
Click to expand...
Click to collapse
Thanks Aragorn.
I think, some applications are not suitable for SU660. Right now, I just uninstalled the Fruit Ninja (Half Brick) and disabled the Background Apps of Yahoo Mail. Everything is Ok Now.
I recharge it through my laptop.
I am using V20m and it is the latest version.
Regards,
Jose Rey
I have the same problem. It regularly happens when Im playing games but when the weather is cold for some reason, it rarely happens. must be hardware.
Hello, I'm using Semaphore + CM10 JB for few weeks (installed with your support).
However I have a problem. The stability. My phone likes to resets byself, even few times per day. It happens irregularly. What's interesting, sometimes phone resets to the CWM. Sometimes resets and backs to work, sometimes totally offs the phone (and i need to pull out the battery) or freeze on cyanogenmod start screen (but not on normal start, only when resets)
Sometimes it happens when i'm using the phone, sometimes not. He likes to do that when i'm sleeping (for example, goes to the CWM and discharge the battery by whole night on full bright).
And much smaller, but maybe important issue: when the phone starts, shows the message Warning! A problem was detected with your device. Your device IMEI number is invalid. And invalid IMEI number could cause network issues including the inability to call emergency numbers.
Firstly I installed CM10, i had the problems with the network, but after @xsenman's help (reinstall with older ROM before flashing CM10) everything works correctly and i can see IMEI too. I made an EFS backup in that old ROM, should i use that? This message doesn't intrude me, but i'm just thinking if this could be connected with reseting problems. My SGS works really nice, but that one issue is really annoying.
100 views and really no one can help?
Come on, i feel so lonely
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
thanks for your answer. However, maybe it's not a ROM problem? Maybe some application makes an issue. Is there any log where i can check that?
That IMEI stuff definitely isn't app-caused. I can only repeat my statement above. Don't worry about data, you can backup everything using Titanium Backup and SMS Backup+.
Btw: What ROM are you on?
Best regards
Sent from my Gameboy Color
True, IMEI not, but it's not a real issue for me. Actually, i'm absolutely satisfied of my i9000 (maybe flashlight absence, but it's hardware). Everything works fine, but reseting problem makes me nervous when I use the phone as car dvr or for endomondo ect.
I use Cyanogenmod 10, one of october's nightly versions.
So basically you don't want to change anything but you want us to help you? Sorry, that's not the way a community works.
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
przemek211 said:
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
Click to expand...
Click to collapse
Since when has this problem occurred? I doubt an app makes a phone reset itself.
Edit: I looked around your post history and you seem to have posted in the semaphore thread. Maybe something is wrong with the kernel?
Sent from my GT-I9000
Thanks for your answer. It's hard to say because I've flash a ROM and out of hand I installed the applications. It's the worst type of problems, because it doesn't happen instantly or regularly. Actually since i wrote the topic, i didn't see the problem, however i saw two-three times the attention about IMEI, so i think, the phone resets, but not seen.
/// amerkiller: you are using i9000 too, could you recommend me any other ROM? Probably I will need to install a ROM and wait, two-three days and check if the ROM makes any issues.
/// maybe, but how can i check it? It looks like work nice, my question in Semaphore's thread was about the features
I use Remics-JB, you can try it out if you want a Samsung touchwiz feel, and apps from the S3.
Slimbean if you want a minimalist ROM.
Hopefully, the problem will disappear.
Powodzenia
Edit: regarding the kernel, you can flash Devil and see if the problem persists.
Sent from my GT-I9000
So I will try Devil + Slimbean, thank you
amerkiller1995 said:
Powodzenia
Click to expand...
Click to collapse
Poles everywhere?
pozdrawiam
BlueFlame4 said:
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
Click to expand...
Click to collapse
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
przemek211 said:
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
Click to expand...
Click to collapse
You can find tutorials about flashing to stock.
http://forum.xda-developers.com/showthread.php?t=1102881
Flashing the stock ROM will recover your IMEI number if you currently don't have it and will wipe your personal files. Backup your IMEI while you're on GB and if you lose it, then restore it. Fyi I never lost my IMEI, it's not common. You should flash JB / cm10 twice, ICS/cm9 should be okay after one flash. Remember to wipe if the instructions say so.
When you'll attempt to flash cm10 in recovery, you'll get a warning about partition change. You'll have to chose to flash second time, this time it should work and the phone will reboot into a bootloop. Pull out the battery and enter recovery and flash cm10 again. This time it well install and reboot successfully.
Sent from my GT-I9000
It's everything working nicely? Asking out of curiosity.
Sent from my GT-I9000
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
przemek211 said:
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
Click to expand...
Click to collapse
Restarts shouldn't happen that was some unusual circumstance. The video problem is weird, post here if it happens again, lets hope its just bad luck.
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
przemek211 said:
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
Click to expand...
Click to collapse
In regards to two way recording, i don't think it's solved...
http://forum.xda-developers.com/showthread.php?t=863074&page=38
I never needed that feature, so i won't be much help, try different apps and remember some apps are on XDA, not only the play store.
Sent from my GT-I9000
I saw that, but it is only for Froyo, when i installed it into gingerbread i needed to re-flash my SGS
I tried a lot of apps, however it looks like being locked (if worked they made 0kB files)