Hi Guys,
My galaxy S3 , SGH-I747M (d2can) is crashing regularly with no warning. I'll give you the symptoms as best I can.
My phone dies only when I'm using it, not when it's in sleep mode. it doesn't have to be a very power-hungry task, though the frequency of the crashes increases when I multitask. There is no lag on the task I'm performing when it crashes, it just looks like the screen has timed out. When I go to restart it right away, I usually only get to the samsung logo, about 6-10 seconds after it boots up. The likelihood that it will stay on after a crash increases the longer I wait with it off after the crash, 30 minutes is usually enough, though pulling the battery seems to help it boot up as well. The battery is not hot when I feel it, it's not even warmer than room temperature which I thought was unusual.
This tends to happen once every two days now
I tried eMMC check and it came back clear.
My phone was rooted shortly after I got it, though the crashes happened even before I rooted it. Just not as frequently, but I also had no apps installed at the time. limiting the background processes does nothing.
Any thoughts? I'm kind of stumped.
This forum is for the d2lte, d2att, and d2can. What is the model for the s3 d2vl? Let us know and we'll try to help.
audit13 said:
This forum is for the d2lte, d2att, and d2can. What is the model for the s3 d2vl? Let us know and we'll try to help.
Click to expand...
Click to collapse
It's the S3 SGH-I747M, which I believe is d2can.
Okay. Your original post mentioned the d2vl.
Are you running a custom ROM? Does it do this on a stock ROM?
audit13 said:
Okay. Your original post mentioned the d2vl.
Are you running a custom ROM? Does it do this on a stock ROM?
Click to expand...
Click to collapse
it's all stock. I just did cf autoroot and twrp. This problem started even before I rooted it.
Sounds like a hardware problem since the issue has always been present.
Definitely seems like a hardware issue. If you still have a warranty, you'll want to get it replaced ASAP (usually the warranty is a year or longer, and some carriers don't care if you've flashed your phone or not). No amount of tweaking will be able to get that thing running properly, most likely.
Sadly it's not under warranty. It doesn't sound like I have any other options than to scrap it. Is it possible to quarantine the bad sector so I can keep using it?
Thanks for all your help btw.
jdezwaan91 said:
Sadly it's not under warranty. It doesn't sound like I have any other options than to scrap it. Is it possible to quarantine the bad sector so I can keep using it?
Thanks for all your help btw.
Click to expand...
Click to collapse
Not unless it was definitely a RAM issue and you had some sort of memory dump that shows exactly when it crashes, and even then, you'd have to manually add things to the kernel to stop it from ever accessing that sector.
It's incredibly hard to do on Linux even, never mind on Android.
You could try undervolting + running different I/O Schedulers and Governors, but I don't know how far that'll get you, honestly.
Related
Well, I stopped on the way home from work today to see what was new at Sprint. I've been thinking about getting the EVO 3D... I came home with a Touch.
So. I want to root, so I can run root apps like um, Ad Free etc. What do I need to know about rooting this before I jump in head first? Do these phones have any stupid security etc or anything I need to know about?
I just wanna make sure I don't mess anything up.
What do we have for a recovery etc?
Any tips would be GREAT!
E4GT doesn't have all the locked bootloader stuff to worry about like EVO 3D.
You can start off here:
[ROOT][EG30] Automated root of your existing stock ROM (w/o ODIN or ROM Flash)
That will get you rooted on stock and won't involve flashing anything. It doesn't use ODIN.
There is also a tool called ODIN which lets you flash stuff to the phone outside of Android. It provides fastboot-like functionality. Using ODIN, if you flash unsigned kernels, your boot screen will get a yellow triangle and there is a flash count that gets incremented. Also it'll identify the phone in the boot screen by the real model name (I9100...) rather Galaxy S2. Other than that it'll still boot and work.
Question about this ODIN flasher thingy and the unsigned kernels. Why the increment count etc? What is the point to that?
Thanks for the info btw. I think the link you sent will be a good start. Don't need to flash any custom roms yet. I wanna get the hang of the stock one first. This Samsung has a very different feel then the HTC EVO/Sense stuff.
Need to ask Samsung.
Probably they want to keep track of whether you installed non-standard software, possibly for service reasons.
---------- Post added at 01:43 AM ---------- Previous post was at 01:35 AM ----------
BTW you can use a USB jig to get rid of the Yellow Triangle and reset the flash counter.
If you just want to get rid of the Yellow Triangle, you can flash back the stock kernel, then use other methods like the Root Installation Kit I pointed to earlier.
Once you get CWM, flashes through that won't affect the Yellow Triangle and flash count.
Just watch the roots right now the odin has an issue with LOS from what I have seen. I am currently using a direct root which roots the rom.
I assume LOS means loss of service?
OK! Noted.
duced said:
Just watch the roots right now the odin has an issue with LOS from what I have seen. I am currently using a direct root which roots the rom.
Click to expand...
Click to collapse
Stock phones suffer from LOS too. Rooting and some kernels MAY make it worse. I've flashed nearly everything available for this device in the last month and have not had 1 serious unexplainable LOS.
Sent from my SPH-D710 using xda premium
OK! Well I did the MOST important thing I wanted to do which was to get root in there so I could use Adfree!
I also did the EG30+CWM5 while I was there. Now what? What cool stuff is there to play with? Looking around the forums now, just not sure what to check out first.
kdoggy said:
OK! Well I did the MOST important thing I wanted to do which was to get root in there so I could use Adfree!
I also did the EG30+CWM5 while I was there. Now what? What cool stuff is there to play with? Looking around the forums now, just not sure what to check out first.
Click to expand...
Click to collapse
If it were me, I would use the phone as is for a few days to get some feel for whether your situation will get LoS and what the battery life is. Then you have a baseline to compare to after you start making changes.
It is easy to get really excited and install a whole bunch of stuff and all of a sudden you get LoS or really bad battery life, and then you can't figure out what caused it or even what to expect with the stock phone.
This could lead you to think the phone is at fault when it is actually something that was installed later.
Also with the official Samsung rom out now most of the roms in development will be getting reworked shortly.
Sent from my SPH-D710 using xda premium
Can someone point me to a thread that explains LOS and what do you do if you get it?
kdoggy said:
Can someone point me to a thread that explains LOS and what do you do if you get it?
Click to expand...
Click to collapse
As far as I know the only thing you can really do is reboot the phone. going back to a stock kernal also helps.
kdoggy said:
I also did the EG30+CWM5 while I was there. Now what? What cool stuff is there to play with? Looking around the forums now, just not sure what to check out first.
Click to expand...
Click to collapse
Install set CPU and underclock that puppy! Especially with the screen off. 200 min has worked flawlessly for me, and 800mhz Max still flies for most things.
The battery savings are staggering.
N00dle said:
As far as I know the only thing you can really do is reboot the phone. going back to a stock kernal also helps.
Click to expand...
Click to collapse
clearing ram fixes it sometimes too
MoMatt said:
Install set CPU and underclock that puppy! Especially with the screen off. 200 min has worked flawlessly for me, and 800mhz Max still flies for most things.
The battery savings are staggering.
Click to expand...
Click to collapse
completely agree. been underclocked to 800mhz for a while. No difference in performance and battery increased probably 20%
MoMatt said:
Install set CPU and underclock that puppy! Especially with the screen off. 200 min has worked flawlessly for me, and 800mhz Max still flies for most things.
The battery savings are staggering.
Click to expand...
Click to collapse
I'll have to give that a try. I've never been into overclocking these phones. I don't game, I don't use them for video either. I just use them for work to look up help desk tickets while I'm going building to building.
Beats the hell out of lugging my MacBook around just to read some notes on the go.
Hy guys I have seen on a noob guide that I can see my phone cpu "stats".
This tells me is my phone a powerfull machine or a bad brick.
So I have installed the faux kernel and with root explorer I came to this t3_variant
/sys/kernel/debug/t3_variant
If your cpu_process_id=
"0"- Sorry, but your in for a world of hurt. I'd recommend only trying out his mainline edition, nothing else.
"1"- Well, you''ll do just fine, but it still sorta shaky. Don't think about overclocking though, unless you're on a beta or VF version
"2"- Knock yourself Out! ;p
"3"- Lock that phone in Fort Knox and, if you see faux lurking around your house, then just run . Jokes aside, your phone can do ANYTHING.
Click to expand...
Click to collapse
This is a quote from a Noob Guide - here.
Mine cpu_process_id=0. Does this mean I bought 4500kn (597.32€ - Yes that's the price of HOX in Croatia) brick?
I have problems with battery he shuts down sometimes more like often, is he really that bad and I am angry right now cause I think I bought bad and expensive phone?!
If you need more info I will be glad to post just someone help me please.
LOL, those cpu variants are to be ignored. They are for hard core overclockers.
It has nothing to do with battery life and you do not own a phone shaped brick. I paid the same amount for my HOX.
Well can you tell me why does he act strange all the time. He just shuts down but he doesn't do that when he is on charger. I think I have some serious power issue. I'will give you all logs you ask and all screenshots just help please.
You might want to try another kernel and do a clean reflash of rom.
Give me the kernel reboot log from /proc/last_kmsg.
No need I think I solved the problem. I have now just moved the governor to interactive witch was default "ondemand". He didn't went off for like 6 hours witch is a record and battery is still 50% can't believe. I know I am noob sry for that
You might wanna try sense roms as well. You wouldnt be facing any random reboots issue.
faiz02 said:
You might wanna try sense roms as well. You wouldnt be facing any random reboots issue.
Click to expand...
Click to collapse
All those random reboots were on stock jb xD
Oh OK,
Case closed.
I haven't had any luck in figuring out an solution to an issue. Maybe someone may have a suggestion to try.
Basically, I'm having an issue with the phone not waking up (coming out of standby). It'll be
I'm running a stock deoxidized rooted (and I think deknoxed because I'm not finding any knox files, but just one directory) NE2 (Android 4.4) rom. The rom is pretty stable with an occasional ramdon reboot.
The problem seems to be tied to WiFi Tether Router. Nice application. The issue only occurs when running this application. It worse when running another application at the same time, which in my case is SiriusXM. From their FAQ section (linky, it looks like it could be an issue of the phone going into some kind power saving management mode. I do not have Power Save mode on. My other guess is there could be a memory leak, but it's beyond my knowledge how to determine if true or not. Although, I do think it's most likely a power management issue because I've other apps stop functioning when in standbye. Sometimes it'll wake up right away hitting the home or power button. Other times, I need to pull or plug a charger to trigger the wake up. Other times, it can take up to 15 minutes. At worse, I have to do a battery pull.
I was thinking maybe I could change the kernel, but don't know of any kernels that are compatible with the stock NE rom. Ultimately, I was to try to change the governor to performance or increase the clock speed. But I think this may not be feasible because, if memory serves me well, those functions need to be build into the kernel.
I would try maybe going ASOP, but I do use a few things that, as far as I know, aren't possible with with them such as screen mirroring. I also don't like some of the have GPS lock issues; I had when I tried an ASOP I had this and a bigger issue. So it's more I don't think it'll meet my needs and wants.
Any ideas would be appreciated.
Try out chaz'es stock rom. I've been using it for 2 weeks no reboots. There is a hot spot mod that you can flash also no app needed.
Sent from my SPH-L900 using XDA Free mobile app
Thanks for the reply. I tried the hotspot mod on 4.3 and tried it once, and it Sprint noticed. Maybe it was the rom or a bad flash. Just quirky.
lovekeiiy said:
Thanks for the reply. I tried the hotspot mod on 4.3 and tried it once, and it Sprint noticed. Maybe it was the rom or a bad flash. Just quirky.
Click to expand...
Click to collapse
There's is a mod specifically for the NE2 update. I would post a link but am on my phone. The mod works great. I haven't had any long term use so I don't know if it notifies sprint.
Sent from my SPH-L900 using XDA Free mobile app
skye206 said:
There's is a mod specifically for the NE2 update. I would post a link but am on my phone. The mod works great. I haven't had any long term use so I don't know if it notifies sprint. ...
Click to expand...
Click to collapse
I"ve used Hotspot mods in the past, so it's not that I'm against them by any means. Just a bit sketchy at the moment. The time I spoke, Sprint sent me a text and a letter about TOS violation. And it wasn't that long ago, so just being a bit careful that's all.
Plus, the last time, I'm not sure if it was the mod, the rom, mod download, or bad flash. Personally, I think it may have been the rom and rom flash. The 4.3 stock rom I used wasn't very stable. A lot of reboots.
With my situtation, I just thinking if I can get the phone not to go into whatever standby or powersave mode when the displays shuts off, would be best. Right now, I'm just not having the display go off, which I really don't like. But I know quite a bit development on the this variant of the GN2 is limited and becoming and less and less everyday. I know others keep more up this stuff than me, thus is why I asked.
As annoying as it may be, I can deal with a little while till my contract ends, which is very soon. Than it's just waiting for the GN4 to release and see what it has, compared to other similar phablets, and the WiFi hotspot to be hacked.
lovekeiiy said:
I"ve used Hotspot mods in the past, so it's not that I'm against them by any means. Just a bit sketchy at the moment. The time I spoke, Sprint sent me a text and a letter about TOS violation. And it wasn't that long ago, so just being a bit careful that's all.
Plus, the last time, I'm not sure if it was the mod, the rom, mod download, or bad flash. Personally, I think it may have been the rom and rom flash. The 4.3 stock rom I used wasn't very stable. A lot of reboots.
With my situtation, I just thinking if I can get the phone not to go into whatever standby or powersave mode when the displays shuts off, would be best. Right now, I'm just not having the display go off, which I really don't like. But I know quite a bit development on the this variant of the GN2 is limited and becoming and less and less everyday. I know others keep more up this stuff than me, thus is why I asked.
As annoying as it may be, I can deal with a little while till my contract ends, which is very soon. Than it's just waiting for the GN4 to release and see what it has, compared to other similar phablets, and the WiFi hotspot to be hacked.
Click to expand...
Click to collapse
Well try a ne2 (4.4.2) rom. Chaz's almost stock rom or my Community 3.2/3.2+ rom and things will be much better as far as usability. Mk4 (4.3) was a garbage release from Samsung. All Samsung devices have issues with 4.3 which is why so many got the 4.4.2 update.
Now about the hotspot. Well I would just stay away from that if I were you. As sprint said it is a TOS violation unless you pay extra for the service.
Sent from my SCH-I605 using XDA Premium 4 mobile app
jlmancuso said:
Well try a ne2 (4.4.2) rom. Chaz's almost stock rom or my Community 3.2/3.2+ rom and things will be much better as far as usability. Mk4 (4.3) was a garbage release from Samsung. All Samsung devices have issues with 4.3 which is why so many got the 4.4.2 update.
Now about the hotspot. Well I would just stay away from that if I were you. As sprint said it is a TOS violation unless you pay extra for the service.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm currently on a stock deoxidized NE2 (4.4.2) ROM. In fact, it may be the same one your referred to by Chaz. I read 4.3 is a mix bad of good and terrible. I waited as long as I could before going to 4.3. If I wasn't having an issue the NHL Center Ice app, I would still be on 4.1.2. 4.3 was always rebooting. I think it had memory leaks.
Right now, the dealing the screen thing is more slightly annoying and inconvenient. It's an issue known by the WiFi Tether Router developer. Even if there was a kernel I could use to do what I want, doesn't necessarily mean my issue would be resolved, since I'm slightly guessing what the problem is.
My thinking too on the hotspot mod. I use way too much data to end up using another mobile service provider. The sent a text saying there was an issue. I had to call Sprint to find out what it was. Since I called and got the letter, I figure I don't have much leeway right now.
I'm not sure if it's a software problem or a hardware problem that's not the motherboard.
This is my phone's original stats, as I have written down.
N7105
ROM: DN3 v3.2
kernal: AGNi v3.9
bootloader: 4.1.2
Recovery: Philz 6.07.9
The problem is that the phone just randomly stopped waking from sleep. Not all the time, but it just started one day and slowly increased in frequency. I eventually figured out that the phone was simply not waking up, causing the phone to (presumably) freak out, because if the freeze happened hours ago, then the phone would be very warm when I picked it up and, after forcibly rebooting via the power button, the battery would be way down.
I noticed IndexServices was using a lot of battery power, and google tells me that it freaks out at files over 200mb in size, but best I can tell, I have no such files. I can't recall anything that would change this when the freezes started happening. It may not be relevant at all.
I could live with the forced reboot for a while, but having my battery capacity killed for no reason sucked.
Screw this, I thought, I have a spare motherboard, I'll figure out the problem later or never.
Nope.
My phone's current stats.
SGH-t889
ROM: DN3 5v2 final slim
kernal: default
bootloader: 4.1.2
Recovery: TWRP 2.8.0.0
I swapped the motherboard in and used Titanium to restore my most-used apps and their data. Unfortunately, the problem seemed to have followed the change, although in a different way. The phone just freezes and doesn't accept any kind of input- no touch, no buttons, nothing. I have to pull the battery to reboot. It doesn't just happen when asleep. I've had the phone literally just stop responding as I was scrolling through a webpage. It seems to happen mostly at night and early morning, which is no bueno. I can't use it as an alarm anymore. But it's still better than leaving it alone only to find the battery down 40%.
It also occasionally reboots on its own. I haven't found a pattern to any of these problems.
I played with this motherboard when installing the ROM and such and never had the above problems, so it may or may not be related to the problem I had with the other motherboard.
It's not my SD card. I pulled it when I still had the N7105 motherboard in. It didn't make much of a difference.
I installed SysLog and got a bunch of logs from the N7105 motherboard right after one freeze/reboot. But I'm not entirely sure what I'm looking at nor what to look for. It's been a while since I've fiddled with my phones, so I'm not very enthused at the idea of reflashing my phone.
What can I do to better pin down the root of the problem, short of reflashing everything and hoping the problem goes away?
I would flash stock rom and kernel without apps restoring just to see if it's hardware or software issue.
there is service menu where you can test sensors *#0*#
you can try to overclock cpu, I remember that some time ago it helped to similiar problems with waking up
Yeah, I think I'll probably have to reflash at some point, just to make sure. But I'm going to avoid it for now, since I have other concerns.
I forgot about the service menu! That's a good idea, thanks!
I've never overclocked a CPU, computer or phone, so I'll read up on that. Not sure it'll help with the t889 motherboard, but it might work for the N7105 motherboard.
Thanks again for the suggestions!
For what it's worth, I have the same problem. It started a few weeks ago. I was using Dr. Ketan's rom and thinking that it might be a rom problem, flashed Resurrection Remix 5.1.1. CM 12.1. For a week there was no problem, but now it's back again.
If the phone is left untouched for a while, it won't wake up and is warm to the touch. And yes, the battery is greatly reduced...
I'll be interested in anything that is discovered....
Thanks.
Well, this is mildly frustrating and not at all helpful, but the weird freezes on the t889 motherboard seem to have stopped by themselves. I didn't do anything beyond poking around the service menu. Everything looked ok there. The freezes continued a while longer, and yesterday I noticed that it had been over a day since I had to pull the battery to force a reboot.
My best guess is that an app update caused a minor hardware incompatibility, and some update this past weekend resolved that incompatibility. I'm going to give it another couple of days before swapping the N7105 motherboard back in and seeing if some app update fixes that problem.
Update: I swapped the N7105 motherboard back in and ran all my app updates. No go; the problem showed up again while I was charging the phone. On the other hand, I was able to confirm without a doubt that it's a problem with this motherboard and not the headphone port that causing the lack of sound output with headphones in. The phone acknowledges the headphones when I plug them in. It just doesn't play anything through it.
Indexservice is still using up far more battery than it should. It might be higher than normal due to all the app updates, but it really shouldn't be as high as it is, so I'm tentatively declaring it related or the cause. Since it's not a file size problem, it may be a corrupted file, which means a reflash in my future, if I want to keep using the N7105 motherboard.
It's possible that all these problems mean that the motherboard is failing. It's two years old. It might just be its time.
Hopefully, reflashing everything will fix the problems. If not, at least I had another motherboard to fall back on.
I'm still having the same problem and haven't found a solution. It often won't awaken and needs a long push on the power button to boot. After booting, if we use it a lot it seems to be fine, but if we leave it alone for a while, it won't wake up.
Is that what you are getting? My wife wants another phone!
We always leave in on the charger all night long (as I have done with all my phones). Can that have damaged something?
I could try flashing a stock rom, but fear this may be a hardware problem. I don't see many participants in this thread...
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
---------- Post added at 06:45 PM ---------- Previous post was at 06:22 PM ----------
That service menu that you quoted above doesn't work on my phone. Could it be misspelled?
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Yes, that is exactly it. As long as I'm actively using the phone, it's fine. It's only when I leave it for a while that it won't wake and I have to press the power button to force reboot.
I also leave my phone on a charger all night, but I hardly think we're the only ones to do this. It might be related, but I kind of think it's not.
You could swap out the motherboard like I did. I imagine they're much cheaper now then they were when I bought mine ages ago. The Note 2 is very easy to take apart.
The service menu as written above works for me. Not sure why it won't work for you.
Did the new motherboard solve the problem completely? I see replacement motherboards for $45 online. They offer both 7100 and 7105. What is the 7105? I now have a 7100 European model.
I downloaded the EMMC check program. My phone does not have the "Insane Chip" that causes the Sudden Death Syndrome, but it has eMMC chip VTU00M -for what that's worth.
Samsung Galaxy S5
Exodus CM12 5.1.1
Boeffla kernel
Apex Launcher
Yes, the problem is completely gone with a new motherboard. Any problems I had with the new motherboard seems to have worked itself out, which is why I concluded that the problem lay with the N7105 motherboard.
I think the difference between the 7100 and 7105 is that the 7105 is the LTE model. There's no harm in buying the motherboard of another model number- I did- you just have to make sure to install the appropriate modems/ROMs for that particular model. (And hey, if you get the 7105- you just upgraded to LTE! Yay!)
Phenomenal. I'm going to order a 7105 motherboard. It will take a while to arrive and my wife will grumpy until it is installed.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Selofain said:
Yes, the problem is completely gone with a new motherboard. Any problems I had with the new motherboard seems to have worked itself out, which is why I concluded that the problem lay with the N7105 motherboard.
I think the difference between the 7100 and 7105 is that the 7105 is the LTE model. There's no harm in buying the motherboard of another model number- I did- you just have to make sure to install the appropriate modems/ROMs for that particular model. (And hey, if you get the 7105- you just upgraded to LTE! Yay!)
Click to expand...
Click to collapse
When you installed the new motherboard, did you have to do anything with your imei number?
In reading above it sounds like you changed motherboards several times and during that time the problem went away, but was it really the different motherboard? There are motherboards for sale in China, but I don't see any indication that they are Samsung manufacture. They are compatible, may be used actually, and although they cost 45€, shipping will be 38€ more unless I want to wait 2 months for the free shipping by mail.
Did you try reflashing a stock rom? I am tempted to try that first.....
Regards
I only have two motherboards, and I only swapped them out a couple of times. I had minor problems with the t889 motherboard at first, but the problem went away on its own after a week or so. It had actually been nearly three weeks before I swapped the N7105 motherboard back in, and I didn't leave it in for long, just long enough to determine that the problem was still there. I'm back to using the t889 motherboard now, and haven't had any problems with refusing to wake from sleep.
I haven't flashed a stock rom yet. I found that I couldn't restore the data of one of my apps to the new motherboard, and the data was something I spent hours inputting, so until I find a way to save that data, I won't be reflashing.
I didn't do anything with the imei when I installed the new motherboard, but I was prepared to transfer the imei if necessary. I backed up my old one and would have restored it to the new motherboard if necessary, but it wasn't necessary, so I didn't do anything. I bought my motherboard on ebay, which has both advantages and pitfalls. I'd say definitely try reflashing first, since that won't cost you anything but time.
My girlfriend has had the same issues for around one week (exactly the same symptoms_freezes when left untouched, especially at night, and she has to reboot). She has been on revolution HD 31 rom for months without problem ; she hasn't installed anything lately either... an update is probably the cause. I flashed ditto N4 (after factory reset) but the issue has shown up again... It's a european n7100.
We have a solution (I think). I did a factory reset and then used Odin to install the most recent 4.4.2 stock rom for Spain (where we live) . I didn't let Google update my applications and installed just the basics that my wife uses. So far so good (12 hours).
Little by little, I will add applications.
This started when we were using Dr. Ketan's excellent modified TouchWiz rom. Apparently some app upgraded itself causing this problem. When I flashed Resurrection Remix, the apps came along with us and so the problem persisted. Wish us luck.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Weird thing, I got that insane chip but my note doesn't seem to randomly reboots overtime.. I experienced some reboots using some rooms, though, mainly with 5.1.1 releases. Is there any trusty app that really informs me the right chip? Thanks.
Enviado do banheiro
Oh, great! It's good to know that it was a software error rather than a hardware error. Let us know if you figure out which app is causing it. It can't be too common an app, or we'd see more people here in this thread.
So far, the phone is behaving perfectly. My wife is thrilled because she is used to the look and feel of Samsung roms. She didn't like AOSP which is considerably more buggy. Yes, with CM12 roms, random reboots are common. Little by little, we are adding essential apps. We don't even have the phone rooted and may not ever do that since my wife likes to keep it simple.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
quijote1 said:
We have a solution (I think). I did a factory reset and then used Odin to install the most recent 4.4.2 stock rom for Spain (where we live) . I didn't let Google update my applications and installed just the basics that my wife uses. So far so good (12 hours).
Little by little, I will add applications.
This started when we were using Dr. Ketan's excellent modified TouchWiz rom. Apparently some app upgraded itself causing this problem. When I flashed Resurrection Remix, the apps came along with us and so the problem persisted. Wish us luck.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
Click to expand...
Click to collapse
I also suspected a touchwiz app update, and maybe a conflict with google play services or a google play services update conflicting now with a touchwiz app (maybe not updated). By the way, did you use hangouts or whatsapp ? and what recovery do you use ?
I have just flashed 'rubbaband_note4_lp_4-4-4_gt-n7100_v1-2.zip' late in the evening, had not enough time to set the phone up as previously, and for the first time it didn't freeze at night...
oliwek said:
I also suspected a touchwiz app update, and maybe a conflict with google play services or a google play services update conflicting now with a touchwiz app (maybe not updated). By the way, did you use hangouts or whatsapp ? and what recovery do you use ?
I have just flashed 'rubbaband_note4_lp_4-4-4_gt-n7100_v1-2.zip' late in the evening, had not enough time to set the phone up as previously, and for the first time it didn't freeze at night...
Click to expand...
Click to collapse
I used the latest TWRP recovery because the AOSP roms seem to like that better. Otherwise I have always preferred Philz. I always froze hangouts but our whole family are heavy WhatsApp users. I have now frozen most of the Samsung and Google bloatware and the phone is very happy. Today root and more apps. Oh, I also use Greenify and it's working fine.
Samsung Galaxy S5
Exodus 5.1.1 AOSP
Apex Launcher
My TMobile Samsung s21fe 5g freezes and reboots repeatedly over and over. It's not boot loop cause it stays frozen for 2 min approximately before reboot. I have hard reset, factory reset,ect and nothing's helped. Please help meee! Thank you
Welcome to XDA.
Does it happen when on the boot menu?
Can it stay on in that state?
Was the firmware recently upgraded or updated?
blackhawk said:
Welcome to XDA.
Does it happen when on the boot menu?
Can it stay on in that state?
Was the firmware recently upgraded or updated?
Click to expand...
Click to collapse
It's starts as soon as I put pattern to unlock in it. It had update couple months ago and was fine but earlier I used Odin and flashed the firmware. Odin said it was successful but the phone gave me this message I will link. Only think I can guess to do is twrp maybe and go from there? Any help would be great and ty!
Try flashing to the original firmware that worked.
If it's not firmware, it's hardware.
A different rom may bypass the damage if that's the cause.
This far more trouble than I ever experienced with Androids. My running rule is to leave the firmware alone, lol with Samsung's it has served me well.
Thank you I will try. Does it matter on rom choice? I have never ran into issues like this unless I caused them trying things I new nothing about lol. With it saying corrupted and the factory reset it but once reset it changes nothing that kinda throws me a little. I'm gonna keep trying due to really like the s21 but that's wearing thin after this. Thanks again
bchatter said:
Thank you I will try. Does it matter on rom choice? I have never ran into issues like this unless I caused them trying things I new nothing about lol. With it saying corrupted and the factory reset it but once reset it changes nothing that kinda throws me a little. I'm gonna keep trying due to really like the s21 but that's wearing thin after this. Thanks again
Click to expand...
Click to collapse
Go back before the most recent firmware upgrade or update.
There are billions of transistors in the SOC, ever wonder what happens if one or more fail?
If this is the case a different rom may not use the damaged area. There maybe no work around if this is the case. It's possible a BGA chipset has a fractured solder joint as well or anyone of numerous possible mobo failures.
Always protect phones from high G load impacts from drops with a good case. These can even cause internal damage to chipsets. Mobos are intolerant to board flexing as well. It's remarkable these devices are as robust as they normally are, all things considered.
Perfect, again thanks so much for input. I am gonna try and see what happens cause that make since. Appreciate your time to me help and take care!