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!
Related
Hi,
I've got my GN for about 2 years now. It always runned fine. I use it essentially to make calls, mails, some european "anti-cop" app called "icoyote", spotify and that's it
Everything stock, full google official, no cracked bull**** apps or whatever.
Ok so now for about 1 month it became less and less stable. It literally happened from one day to another. I guarantee i didn't add/change or remove anything.
Main issues are : spotify crashes many times (~20 to 50) a day and 50% of the time the GPS fix fails to go trough, but a simple reboot and it work's instantly.
So I tought I should make a full factory reset. I did that and the issues I was experiencing remained the same.
Now comes the 1million $ question : how the heck can something stop to work from one day to another ? If it was some *unpredicted*, classic hardware failure, a simple reboot would definitely not solve it, for sure.
Leading to think it has to be software related..OK, so a factory reset should solve : it doesn't neither.
Why are those apps crashing even in a very stock/factory config? I even did skip this google restore profile bull**** to be sure i'm workng in a perfect clean state.
The only logic conclusion is that there must be some kind of hard coded counter which reached the end and is now triggering randomly something, *i don't know based on what, or activated how* making this **** happen
It's very very very frustrating because it was working like a charm those past 2 years and i thought it was a good investment. I was obviously wrong, another death scheduled device.
Now with the 4.3, I got the feeling it becomes even worse. Today, I had to reboot 4 times to get a gps fix (working 100% of the time just after the reboot) and it was a hassle to get trough 2 songs without being cut off in the middle of it.
FU samsung
But you only tried to flash 4.3. It's like giving a patient only 1 medicine and when that not works declare him dead. There maybe other ways to revive your phone..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
But you only tried to flash 4.3
Click to expand...
Click to collapse
when did i say that ? i'm done by years flashing a tool I use to work with. i'm not using it as a toy.
i received the update ota
there's nothing left to try, since my last basic test's where made in a official google factory default situation on a google phone
it's just stock u see? everything else i could try from this point would lead to a non-default situation making every further considerations totally pointless
Well, if i'm right, the so called "crash-routine" would *maybe* not be present in a custom rom, but, again, it worked before and has to work the same way now.
I refuse to use any other workarounds than factory resetting it and, since i already did that a few times, i'm done
i'm not awaiting some kind of help here. i'm just exposing my case and the frustration i'm feeling since samsung nicely dry-fcked me ^^
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Read this. It's called Planned Obsolescence. Manufactures purposely make devices with limited lifespan in order to upgrade to their next new device.
http://en.m.wikipedia.org/wiki/Planned_obsolescence
Sent from my Galaxy Nexus using Tapatalk 2
Fastboot, Odin, omap.. All stock..
Sent from my Galaxy Nexus using XDA Premium HD app
johno86 said:
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Click to expand...
Click to collapse
I ain't here to help either, i just couldn't agree more with what he said above... and its 2013, everyone knows that every electronic sh*t comes with a limited life span, if you didnt know that until now, i'm not sure where you been living..
Peace \m/.
Try wiping your SD card
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.
i need help! ill donate a little cash to the first person that finds a working solution im absolutely stumped on this. two weeks ago i tried upgrading my rooted sprint note 4 from android 4.4.4 to lollipop and everything seemed to go well until i opened up the camera and i went in to a bootloop. since then it hasn't stopped. i have tried flashing stock tars with odin. ive tried CM roms, noterized rom, tons of roms with custom recovery. ive used windows xp, and windows 7, 2 different computers, different cables, different usb ports. odin with administrator rights. nothing will stick. ive gotten passes and fails with odin. when it passes the phone will work as long as im on a charger after first boot once it comes off the charger it immediately goes in to a bootloop and then will not go past the samsung logo and if it does it reboots at the Spark logo. ive wiped cache 3x and factory reset 3x prior to flashing ive checked threads for the past two weeks and only made this account to ask for help. im not new to rooting and have never encountered and issue like this before. i can get in to download mode and recovery so i still have hope its just beyond my knowledge. occasionally recovery bootloops unless im on a charger as well. can someone PLEASE help me?? its making my stomach sick. my only option for internet is a galaxy s5 i bought with root for hotspot so everything i do takes forever to download. sorry for the legthy post im just trying to be detailed as possible for what ive already tried. like i stated above ive done my research this is my last option. thank you.
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
ianmb said:
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
Click to expand...
Click to collapse
i was thinking that as well but with my luck figured that would be too easy of a solution and weird that it decided to go ploop immediately after the flash. i play XBL off my hotspot and it can get rather hot. i usually keep an ice pack with a piece of cloth under it when i run it for an extended period of time though. ill buy a cheap one on ebay as a test. appreciate your input.
ianmb said:
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
Click to expand...
Click to collapse
hey the stupid battery was the issue. dm me your PayPal if you'd like and I'll throw you a couple dollars for a beer or something. I feel like an idiot.
AssmanProctologist said:
hey the stupid battery was the issue. dm me your PayPal if you'd like and I'll throw you a couple dollars for a beer or something. I feel like an idiot.
Click to expand...
Click to collapse
Not a problem. Just glad to help out. Keep your money bro, times are hard for some.
Is it safe to do a factory reset via stock recovery straight out of the box... it won't lock the phone? Or should I first start it, do a fast set up and then do a factory reset?
Anyone?
mk89pwnz said:
Anyone?
Click to expand...
Click to collapse
I'm not going to jump straight into a reset. I had the boot loop problem and wiping the cache from recovery finished the phone off for good. DM verity error, failed to set up dirty target etc. Been unusable since. I'm personally not going to touch any recovery options until the stock levels are high so I can get a replacement straight away if something goes wrong. I'm sure they'll have addressed the issue with the firmware but not going to take the risk just yet.
zanderswigan said:
I'm not going to jump straight into a reset. I had the boot loop problem and wiping the cache from recovery finished the phone off for good. DM verity error, failed to set up dirty target etc. Been unusable since. I'm personally not going to touch any recovery options until the stock levels are high so I can get a replacement straight away if something goes wrong. I'm sure they'll have addressed the issue with the firmware but not going to take the risk just yet.
Click to expand...
Click to collapse
I was thinking about the same... if I get a bootloop then I'am doomed. I want to do this because a lot of ppl are saying it improves the battery life drastically but they mi might be wrong. BTW have you tired flashing stock firmware with odin or using Samsung smart switch? Imo it should fix the problem!
mk89pwnz said:
I was thinking about the same... if I get a bootloop then I'am doomed. I want to do this because a lot of ppl are saying it improves the battery life drastically but they mi might be wrong. BTW have you tired flashing stock firmware with odin or using Samsung smart switch? Imo it should fix the problem!
Click to expand...
Click to collapse
Yeah tried absolutely everything mate. Tried emergency recovery which got to 100% on the pc. When the install started on the device it sticks at 32% then restarts back into recovery. Exact same thing when I flashed the AP via Odin. Completely bricked
zanderswigan said:
Yeah tried absolutely everything mate. Tried emergency recovery which got to 100% on the pc. When the install started on the device it sticks at 32% then restarts back into recovery. Exact same thing when I flashed the AP via Odin. Completely bricked
Click to expand...
Click to collapse
That's rly sad... I will wait for a month and see how is the battery and then do a factory reset if I'am not getting good SOT. Rooted a lot of sammy devices can a lot of bootloops few bricks but if I managed to get in dl mode odin always saved me, maybe it has something to do with the battery problem?
mk89pwnz said:
That's rly sad... I will wait for a month and see how is the battery and then do a factory reset if I'am not getting good SOT. Rooted a lot of sammy devices can a lot of bootloops few bricks but if I managed to get in dl mode odin always saved me, maybe it has something to do with the battery problem?
Click to expand...
Click to collapse
I have read elsewhere that Samsung were initially pulling the mother boards out and replacing them to fix this issue. By the time mine died theyd recalled them worldwide anyway so they weren't interested in repairing it only to have to replace it.
zanderswigan said:
I have read elsewhere that Samsung were initially pulling the mother boards out and replacing them to fix this issue. By the time mine died theyd recalled them worldwide anyway so they weren't interested in repairing it only to have to replace it.
Click to expand...
Click to collapse
Maybe that's why it's a world wide recall mb problem + battery... rly sad that such a beast is having so much problems... BTW what is your note version?
mk89pwnz said:
Maybe that's why it's a world wide recall mb problem + battery... rly sad that such a beast is having so much problems... BTW what is your note version?
Click to expand...
Click to collapse
Yeah it's a much more widespread problem than the battery exploding it would seem. Affecting lots of people to varying degrees. Definately a massive part of why they've had to recall them. The battery issue means they get to use safety as the main driver instead of actually having to acknowledge there is a catastrophic problem with motherboards or firmware whatever it is that's causing the reboots. I have the exynos with the single sim. Uk version in blue. Yourself?
zanderswigan said:
Yeah it's a much more widespread problem than the battery exploding it would seem. Affecting lots of people to varying degrees. Definately a massive part of why they've had to recall them. The battery issue means they get to use safety as the main driver instead of actually having to acknowledge there is a catastrophic problem with motherboards or firmware whatever it is that's causing the reboots. I have the exynos with the single sim. Uk version in blue. Yourself?
Click to expand...
Click to collapse
Will be the same 930F the international one. That doesn't sound very good. Can't wait to get mine and test it out.
Maybe someone tried the factory reset on the new note 7?
Bump... anyone tried factory reset with stock recovery out of the box?
I was thinking about factory resetting my new N7 out of the box. Not sure I will though - would like to know the ramifications (good and bad). My original N7 has great battery life and no issues so IDK if should even mess with a factory reset to start with.
I factory reset from recovery on both my exchanged AT&T Note 7s at the store when exchanging, and then again when I got home and have had not a single issue.
mk89pwnz said:
Bump... anyone tried factory reset with stock recovery out of the box?
Click to expand...
Click to collapse
Im not sure what the big deal is here.....go ahead and reset it...it will do what it always does and has always done.
No more no less and the first thing i do when i get a new device.
If you set up then reset the only extra thing it will do is undo everything you just set up lol.
Kinda of counterproductive if anything.
Sent from my SM-N930F using Tapatalk 2
force70 said:
Im not sure what the big deal is here.....go ahead and reset it...it will do what it always does and has always done.
No more no less and the first thing i do when i get a new device.
If you set up then reset the only extra thing it will do is undo everything you just set up lol.
Kinda of counterproductive if anything.
Sent from my SM-N930F using Tapatalk 2
Click to expand...
Click to collapse
Just paranoid Was waiting for the phone so long if it bootloops then I'am f... Anyway will try booting on then going to recovery and do the wipe
Okay, so I have no idea what is wrong with my att note 4.This thing has always been kept in an otterrbox.It has been kept in perfect condition until an ota forced its self upon the phone. After that it started acting weird. Reboots, freezes, black screens, and sometimes something would get corrupted and the phone wouldn't boot at all. Sometimes the phone would make a constant buzzer or it would go straight to recovery but say sbl1 partition doesn't exist. Flashing stock worked for a while, but the problems would come back shortly and have gotten much worse.I just bought a brand new battery fully charged it and flashed stock 5.0, 5.1, 6.0. It doesn't matter i have tried it with the pit, without the pit same things happen. I have tried both batteries, fresh wipes, different firmware's, and now I can't even get it to boot at all no matter what I Try.
What do you guys think my problem could be i have no idea what it could be
I WOULD APPRECIATE ANY HELP
Same Issue
Hello,
After the marshmallow update I am facing the same. but i kept it running by downloading wakelock app from playstore . It somehow helps I am not sure the reason. Please select PARTIAL_WAKE_LOCK option once you download.
Try to not to shut down the phone because of any reason.
I hope this helps! and do let me know if it does.
my phone has been doing this for the past year after the update to 5, I purchased it on ATT Next in december 2014 so I think i have 1 more next payment. thing is it was the BEST phone prior to the update to 5 then it has been hell. i've purchased 5 batteries which someitmes helped for a short period but currently i can't even use any of my tricks to get it to boot.
I have came so close to crushing the phone so many times. thank goodness ii'm older and wiser or else it would be long gone
jammer8 said:
my phone has been doing this for the past year after the update to 5, I purchased it on ATT Next in december 2014 so I think i have 1 more next payment. thing is it was the BEST phone prior to the update to 5 then it has been hell. i've purchased 5 batteries which someitmes helped for a short period but currently i can't even use any of my tricks to get it to boot.
I have came so close to crushing the phone so many times. thank goodness ii'm older and wiser or else it would be long gone
Click to expand...
Click to collapse
I have read many sources available online. These updates sometime is not compatible with our phones. In case of note 4, certain model's CPU faces shutdown trouble due to update the moment we lock the screen or in standby mode. To keep them running there are apps like wakelock. Download that and select option Partial_wake_lock. This will help a bit hopefully. Worked for me. But this isn't a permanent solution.
Apologies in advance if my terminologies aren't correct or the solution doesn't work.