I did some searching, and found other people having issues with their Galaxy S3 rebooting randomly, but they were having that issue with CM 11. Since I'm still on 10.2, though, the methods that they suggest (mainly installing the updated gapps for CM 11) won't work.
Heres's the background info:
I'm on Sprint, and have been having issues with LTE reception ever since I switched from Touch Wiz to CM back in October. The issue started a couple weeks ago when I found out that the MK3 modem was available. I was still on MD4, and having issues with LTE reception, I thought this new modem would help. I downloaded an install zip file I found on this site and used CWM to install it. That same day I also found out about an updated apns-config.xml file that had helped out other people that used Sprint/Ting with LTE reception. I found that file here (I'm still considerd a new user, so replace _ with a period):
help_ting_com/entries/23423026
The install zip that I downloaded from that site didn't work, so I backed up the original apns-config.xml, and manually replaced it with the new one. I had to change permissions on a couple folders in order to replace it, too.
That day is when the random reboots started happening. I've since reverted back to the MD4 modem, and have also reverted to a backup of the old apns-conf.xml. I've also changed the permissions to the system and system/etc folders to what they were before, as well. The random reboots keep happening, though.
Any help would be amazing.
cbellk said:
I did some searching, and found other people having issues with their Galaxy S3 rebooting randomly, but they were having that issue with CM 11. Since I'm still on 10.2, though, the methods that they suggest (mainly installing the updated gapps for CM 11) won't work.
Heres's the background info:
I'm on Sprint, and have been having issues with LTE reception ever since I switched from Touch Wiz to CM back in October. The issue started a couple weeks ago when I found out that the MK3 modem was available. I was still on MD4, and having issues with LTE reception, I thought this new modem would help. I downloaded an install zip file I found on this site and used CWM to install it. That same day I also found out about an updated apns-config.xml file that had helped out other people that used Sprint/Ting with LTE reception. I found that file here (I'm still considerd a new user, so replace _ with a period):
help_ting_com/entries/23423026
The install zip that I downloaded from that site didn't work, so I backed up the original apns-config.xml, and manually replaced it with the new one. I had to change permissions on a couple folders in order to replace it, too.
That day is when the random reboots started happening. I've since reverted back to the MD4 modem, and have also reverted to a backup of the old apns-conf.xml. I've also changed the permissions to the system and system/etc folders to what they were before, as well. The random reboots keep happening, though.
Any help would be amazing.
Click to expand...
Click to collapse
When I 1st flashed a cm11 based rom, I had random reboots. I solved the problem by changing kernel governor from interactive to on demand. I have not had a single reboot in months. All phones are built differently though. I've had mine since they 1st came out.
sent from my GS3
Jessooca said:
Does your phone get to the Samsung logo and reboot?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Nope, it's the CM logo.
joeyhdownsouth said:
When I 1st flashed a cm11 based rom, I had random reboots. I solved the problem by changing kernel governor from interactive to on demand. I have not had a single reboot in months. All phones are built differently though. I've had mine since they 1st came out.
sent from my GS3
Click to expand...
Click to collapse
Thanks. I tried this, and it didn't seem to work. Phone's still randomly rebooting. I'm on 10.2, btw. Haven't moved to 11 yet.
Jessooca said:
The best way to truly fix your issue is to start back over at square 1... Odin it back to stock with the tar or MD5 file. The last thing you want to do is make things worse trying too many things.
If you can get back into recovery wipe everything, (but not your Sd card ) as long as you've got a Rom on your Sd card to flash. Don't flash the same rom again, your issue could be a number of things.
- If you made a backup before flashing then revert back to it. Then try to download the rom again, or if you can download the latest slimkat on another pc and copy it to your sd card it's small a quick download and it will get you back up and running.
That is, if you don't feel like using Odin.
Click to expand...
Click to collapse
So I wiped, and started over, and then restored data, but the random reboots are still happening. Should I not have restored data? I'd like to avoid losing everything if I could.
cbellk said:
So I wiped, and started over, and then restored data, but the random reboots are still happening. Should I not have restored data? I'd like to avoid losing everything if I could.
Click to expand...
Click to collapse
Data restore could very well be the culprit.
sent from my GS3
joeyhdownsouth said:
Data restore could very well be the culprit.
sent from my GS3
Click to expand...
Click to collapse
So I'd have to start from scratch? Is there any way I could keep my data?
Related
I have seen a variety of posts in various threads about people not being able to get GPS connections and blaming the ROM they were on the for the problem - I imagine that sometimes that could be the reason but something happened to me recently that makes me wonder...
I am a flashaholic - often going back and forth between various ROMS via Nandroid back ups - all was good - then recently I noticed my GPS wasn't working. I thouht it was the rom - but no matter what I did I could not fix it. I tried installing other roms - totally clean install - I tried flashing back to rooted stock and no matter what I tried, GPS did not work.
I don't know where I saw it, but I finally saw a post from someone who suggested fixing it by going back to stock via odin - I tried that and it didnt work either - digging a little deeper someone suggested using odin to going back to pure stock then go into settings and do a factory restore.
I tried it - and it worked - took me virtually all day to figure it out - but it is working better than ever now - I wish I knew what caused it in the first place - but at least I found a somewhat reasonable solution.
If you have lost your GPS and can't get it working again - give it a shot -
Does anyone else have any other suggestiions that might work?
This is correct. I had this exact same issue and this worked for me as well.
Tyie101 said:
This is correct. I had this exact same issue and this worked for me as well.
Click to expand...
Click to collapse
Do you know why it happend in the first place? Was it the result of a specific Rom or just flashing in general?
Thats what i found that worked for me too. It only worked after i went into settings and reset the phone after odin.
Sent from my SGH-I747 using xda app-developers app
I heard it was sprint based leaks on the s3
pure stock ?? can you explain ..thanks
mocsab said:
I have seen a variety of posts in various threads about people not being able to get GPS connections and blaming the ROM they were on the for the problem - I imagine that sometimes that could be the reason but something happened to me recently that makes me wonder...
I am a flashaholic - often going back and forth between various ROMS via Nandroid back ups - all was good - then recently I noticed my GPS wasn't working. I thouht it was the rom - but no matter what I did I could not fix it. I tried installing other roms - totally clean install - I tried flashing back to rooted stock and no matter what I tried, GPS did not work.
I don't know where I saw it, but I finally saw a post from someone who suggested fixing it by going back to stock via odin - I tried that and it didnt work either - digging a little deeper someone suggested using odin to going back to pure stock then go into settings and do a factory restore.
I tried it - and it worked - took me virtually all day to figure it out - but it is working better than ever now - I wish I knew what caused it in the first place - but at least I found a somewhat reasonable solution.
If you have lost your GPS and can't get it working again - give it a shot -
Does anyone else have any other suggestiions that might work?
Click to expand...
Click to collapse
I recently lost my GPS after flashing a Sprint-based ROM. Unfortunately, ODIN back to stock and factory reset from the Settings menu (and from recovery) did not bring back my GPS.
However, I followed a suggestion from this thread:
http://forum.xda-developers.com/showthread.php?t=1923067
I used ODIN to go back to a rooted stock ROM, installed CWM, installed the Sprint-based ROM that seemed to have been the source of the trouble. My GPS started working again. I then used CWM to restore a stock nandroid backup I had from earlier and GPS continued to work thereafter in any ROM I flashed.
There may be a simpler process, but that's what worked for me.
frelnik said:
I recently lost my GPS after flashing a Sprint-based ROM. Unfortunately, ODIN back to stock and factory reset from the Settings menu (and from recovery) did not bring back my GPS.
However, I followed a suggestion from this thread:
http://forum.xda-developers.com/showthread.php?t=1923067
I used ODIN to go back to a rooted stock ROM, installed CWM, installed the Sprint-based ROM that seemed to have been the source of the trouble. My GPS started working again. I then used CWM to restore a stock nandroid backup I had from earlier and GPS continued to work thereafter in any ROM I flashed.
There may be a simpler process, but that's what worked for me.
Click to expand...
Click to collapse
Now that I thnk of it, I also had flashed a Sprint Based rom - that must have triggered my original issue - I explained what I did to restore my GPS at the start of this thread _ and it is similar to what you described - execept I did not odin to a SPRINT rom - I used ODIN to bak to pure stock - then did a factory restore - (and this second step is what seemed to do the trick) then I re-rooted and went backto my happy days of flashing roms - I haven't had an issue since.
mocsab said:
Now that I thnk of it, I also had flashed a Sprint Based rom - that must have triggered my original issue - I explained what I did to restore my GPS at the start of this thread _ and it is similar to what you described - execept I did not odin to a SPRINT rom - I used ODIN to bak to pure stock - then did a factory restore - (and this second step is what seemed to do the trick) then I re-rooted and went backto my happy days of flashing roms - I haven't had an issue since.
Click to expand...
Click to collapse
so what all of you are saying its only because you flashed that sprint leak and thats why ur gps was all jacked up?
amzi said:
so what all of you are saying its only because you flashed that sprint leak and thats why ur gps was all jacked up?
Click to expand...
Click to collapse
Well...that may not be the cause but it's a common denominator. I did and I had to flash back to stock and factory wipe to get mine back.
rpavich said:
Well...that may not be the cause but it's a common denominator. I did and I had to flash back to stock and factory wipe to get mine back.
Click to expand...
Click to collapse
It definitely seems to be a common element to most of these GPS issues. I'm not sure why, in some cases, all it takes is a factory reset in stock to fix it, while others have to re-install the Sprint ROM first. Either way, though, it seems like in most cases, it's user-fixable.
Got the GPS death syndrome today. Flashed a ton of stock ICS nandroid backups without any luck. Finally fixed it after flashing a Sprint JB ROM nandroid then back to ICS. Such a werid issue.
Why flash a Sprint ROM on an ATT phone though?
NYYFan02 said:
Why flash a Sprint ROM on an ATT phone though?
Click to expand...
Click to collapse
Because its the only official US Jelly Bean released at the moment.
It was one of the many backups I had. Don't know why it fixed it but it did.
I have the same issue. Now to flash a stock rom using Odin, do you have to use the toolkit? Also where can I download a Rogers stock rom from?
finally after losing gps and reading thread after thread got it to work , thank you to the guys that personally try to help , dont know why it struck this time but it did , now i will try to bring it back to stock , again thanks , by the way the rom i was using to bring it back was serenity 1.1 which i use before but wouldn't stick...:good:
xtwo said:
I have the same issue. Now to flash a stock rom using Odin, do you have to use the toolkit? Also where can I download a Rogers stock rom from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1968625
Canadian roms are on page 2
Gps still not working
I downloaded the stock Rogers rom and using Odin through toolkit I flashed the stock rom on my Rogers s3. The root is gone and it's back on stock but I still can't use gps. Also now I'm also unable to use ttorents What else can I do to fix this issue?
xtwo said:
I downloaded the stock Rogers rom and using Odin through toolkit I flashed the stock rom on my Rogers s3. The root is gone and it's back on stock but I still can't use gps. Also now I'm also unable to use ttorents What else can I do to fix this issue?
Click to expand...
Click to collapse
If your problem started after installing a Sprint-based ROM, then root your phone, install CWM and then install that same Sprint ROM. Your GPS will probably work after that. You can then restore a Nandroid backup of another ROM. That's how a lot of us were able to fix our GPS.
Sent from my SGH-T999 using xda app-developers app
thanks for figuring this out, I've been struggling to get it working a few days now
Sent from my SGH-I747 using xda app-developers app
I was running latest paranoid android and I wiped cache/dalvic cache after flashing Cerberus in recovery and when the phone booted up it was asking me to Activate (sprint service) my phone. I've never seen this with flashing roms and was wondering if this is a known issue with flashing roms on the S3 or something that can randomly occur from time to time.
Anyone have experience with this before? I had been running Paranoid Android for less than 24 hours but initially didn't have any problems whatsoever.
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
youdoofus said:
Itll do that sometimes depending on the rom. Usually does it after a factory reset and installing a cm based rom. Its just asking you to add your google account... you should be fine
sent from my thumbs
Click to expand...
Click to collapse
This didn't have anything to do with my Google account. I guess I should have been more specific, I mean that my phone is deactivated on Sprint's network as in I can't make phone calls and all the info is missing in about phone. Phone number, PRL and such. I am flashing back to stock right now and hope this fixes it. Will probably give paranoid another go but this doesn't sound like a common issue because I haven't been able to find anything by searching.
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Ahhh... could try manually flashing your modem after the install too
sent from my thumbs
billard412 said:
When you get back to stock it'll probably reactivate itself. If not (although you can do this regardless just in case), ##72786# in the dialer should set you straight. If I'm not mistaken the screen you're referring to should be gone when you boot stock regardless. Its a bug. Doesn't work for a sprint phone but still buried in the rom
Click to expand...
Click to collapse
Soon as I flashed the stock rom it tried to activate and initially failed and prompted me to reboot. Second attempt it was successful and then I immediately flashed back to PA and it is working. Going to give it another shot and keep the stock rom on my sd card this time in case I get stuck in a pinch.
I jumped the gun, phone activated fine but signal drops in and out randomly and will not connect to 3g. Just reflashed to stock again and everything seemed fine but signal was still back in and out. Checked under status and PRL read "0" tried updating to no avail so did the dialer code and it did the activation and all is right in the world again, or at least for the moment.
Just trying to figure out why when I flash Paranoid all my settings just disappear
*edit*
Just flashed back to PA this third time after fully making sure that the phone was working and had 3G data and all was right with the world (my phone). Will update if it goes South again but as of right now the phone is behaving properly. Maybe it just wasn't working right the first time and I didn't notice since I was on wifi. Only thing that keeps me from thinking that is I didn't get the Activation message until 12 hours or so after I had flashed and had been using the phone. /shrug
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
youdoofus said:
I still think flashing a modem in recovery after installing PA would yield a poisitve result
sent from my thumbs
Click to expand...
Click to collapse
how do you flash a modem? I am new to this and this is also a problem that I am having with the same rom. I tried searching for a fix and this is where i landed.
Thank you,
and sorry if i am breaking forum rules
Solved! ODIN'd back to stock and LTE kicked in immediately. Back to flashing =) Thanks guys!
Original Post:
============================================================================
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
hednik said:
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
Click to expand...
Click to collapse
Thanks for the reply. I just downloaded root-injected stock and am flashing as we speak. If this doesn't work, I'm going to flash back to bone-stock and see how that goes. I'll report back and let everyone know =)
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
peaster3 said:
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
Click to expand...
Click to collapse
I'm getting LTE speeds, problem is after toggling airplane mode or rebooting the phone it takes up to 10 minutes for LTE to activate. I fresh installed GalaxyMod, wiped everything possible in the wipe menu of TWRP with the exception of external SD.
I also applied the LTE fix before I booted GalaxyMod, but I did not flash KT747. I prefer to not flash that kernel because it has the updated BT/WIFI drivers and had a warning that I would need to back those drivers up if I ever wished to revert. I don't really feel like going through all of that lol.
Solved. ODIN'd back to stock =) Thanks hednik!
RPelham said:
Solved. ODIN'd back to stock =) Thanks hednik!
Click to expand...
Click to collapse
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
hednik said:
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
Click to expand...
Click to collapse
Yupp I haven't yet lost my IMEI since I got the phone back in July. Guess I'm lucky so far, see posts all the time where people lose it, and I'm a flashaholic lol.
Sent from my SGH-I747 using xda app-developers app
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).
Here is my problem on 4.3 roms, i have no trouble installing them and the load up perfectly but after i do a restart i cant get past the boot screen. It does it on all 4.3 roms, i have the latest twrp recovery latest modem and stuff everything is up to date only have this problem on 4.3 ive formatted the internal storage numerous times and always followed op instructions. i cant find anyone else with this problem any help is appreciated tia
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
joeyhdownsouth said:
The only time I had this issue was after I changed font in Rom Toolbox. How are you wiping?
sent from my GS3 running Illusion4.3
Click to expand...
Click to collapse
im using twrp first i tried to factory reset, caches that didnt work i formated internal storage same problem everything works great untill i restart the phone then wont go past boot screen. like its not reading the internal drive even did fix permisions and wiped caches after install. Also i used the updated su to flash after still problems, beyond me no problems with older ones or tw just the 4.3 roms
I, also, am having this very same issue. I'm honestly surprised that noone else seems to have run across this issue.
Installing is never an issue, running is never a problem, but if I ever reboot, if a ROM reboots itself, I'm left stuck at the GalaxyS4 splash screen, and the only way out it to Wipe everything and reinstall.
I see youre posting from an S3, I am using an AT&T S4.
Clearly, the issue is related to 4.3...
I had that problem with an unofficial build. But that was a bad download. Do you have new phones? The mount points are different on the newer sg3's. There's a thread with a fix for that
i had that problem. for some reason it locks your recovery and internal storage. you have to wipe it and install a rom via odin to work again. thats why im staying away from 4.3
i got my phone last december so its not real new, guess Ill just stay away from 4.3 roms. my recovery never got locked it just wont boot back up after restart. thanks for all the ideas