Hey, XDA-ers!
I got the Android Nougat 7.0 update for my Samsung Galaxy S7 SM-G930FD (DUOS) back in January if I remember correctly. And the update process went like how it normally does. But ever since I got the Nougat update, my phone restarts randomly for no reason. At first it used to restart when I click on the 'Recent Apps' button to switch between apps. When I tap on the button, the phone vibrates and restarts. The phone never over heated before this happens. During this, the phone used to restart 2-3 times a day. This went on for 2 months. Then now, the number of restarts reduced to 1-2 per day, but the problem still persists. And now, it restarts even when I don't touch the 'Recent Apps' button. So, if any of you has had a similar experience or if any of you could help me out Please share it here. It would be GREAT!
Also just one more thing- Any of you seen any DRASTIC or worse changes in battery life of your Galaxy S7 after the Android Nougat 7.0 update? Please share your thoughts here and do suggest how you solved the problem. (My battery drains so fast that I sometimes charge it twice a day. I don't even use my phone for half of the day because I'll be at school and still the battery drain is bad! )
Factory reset. Backup your data via kies and then reset it.
Change your battery
What firmware version are you running? There's at least one version of Nougat that has issues with this
https://forum.xda-developers.com/galaxy-s7/help/random-reboots-nougat-update-t3584333
Us3rNam3d said:
Factory reset. Backup your data via kies and then reset it.
Click to expand...
Click to collapse
Hey, man!
I already tried it like 3 times now. No luck!?
CurtisMJ said:
What firmware version are you running? There's at least one version of Nougat that has issues with this
https://forum.xda-developers.com/galaxy-s7/help/random-reboots-nougat-update-t3584333
Click to expand...
Click to collapse
Hey man!?
The screen shot attached has my software info. Check it out and tell me if it's one of the versions with the problem.
Thanks!
Hmm... and after the factory reset with no apps installed you are still rebooting?
Why dont you try to reflash your firmware via odin.
Download it from sammobile and reflash it.
AgentArjun56 said:
Hey man!?
The screen shot attached has my software info. Check it out and tell me if it's one of the versions with the problem.
Thanks!
Click to expand...
Click to collapse
Possibly. I can vouch for it being fixed on DQCF onwards, which is newer than DQC4. The temporary fix seems to be to use as little RAM as possible(try to cut down on background apps until the next update). That firmware isn't terribly old though. I would actually agree with trying a reflash first.
CurtisMJ said:
Possibly. I can vouch for it being fixed on DQCF onwards, which is newer than DQC4. The temporary fix seems to be to use as little RAM as possible(try to cut down on background apps until the next update). That firmware isn't terribly old though. I would actually agree with trying a reflash first.
Click to expand...
Click to collapse
I think it is also possible to reinstall the same firmware with Smart Switch from the menu "Emergency Software Recovery and Initialisation". It's like Odin but much simpler especially for beginners. As for me, I am still in DQBO and I await the update DQD7 which is beginning to be deployed in some countries. If this is not going to solve the problem, I will try to reinstall the fimware with Smart Switch. What do you think ?
GeekTN said:
I think it is also possible to reinstall the same firmware with Smart Switch from the menu "Emergency Software Recovery and Initialisation". It's like Odin but much simpler especially for beginners. As for me, I am still in DQBO and I await the update DQD7 which is beginning to be deployed in some countries. If this is not going to solve the problem, I will try to reinstall the fimware with Smart Switch. What do you think ?
Click to expand...
Click to collapse
If it's restarting due to the firmware bug then DQD7 will most definitely fix it. Beware of the emergency recovery though. Ive not used Smart Switch but the "initialization" part sounds like it would wipe the device, though that could fix any issues. Backup first, if you can.
Related
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Hello I have a Galaxy S7 and since the update to Android Nougat 7.0, my phone restarts randomly, it can stay an entire week without restart and it can also restart 2 days in a row. It's totally random. I have reset to the factory settings and I have reinstalled only the most important applications (facebook messenger, viber, yahoo mail) but unfortunately about ten days after reset, the problem has reappeared. What could be the cause of this problem? For info, the firmware version installed on my phone is: G930FXXU1DQBO. Also, I saw on SamMobile that the countries that received the update later, had a new version. Could the problem come from that? Is this a bug in the firmware installed on my Galaxy S7. Thank you in advance for your help.
Have the same problem, I'm on G935FXXU1DQB1.
Sent from my SM-G935F using Tapatalk
Vichenec said:
Have the same problem, I'm on G935FXXU1DQB1.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply Do you reset your phone too? And what is the average frequency of restarts?
Didn't do anything as it doesn't bother me that much.
Sent from my SM-G935F using Tapatalk
Vichenec said:
Didn't do anything as it doesn't bother me that much.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
It is still binding Once I had this problem while I was on call!
I have a thread about this, it was unusual for me too, theese random reboots.
After the third reinstall, (first one everyday rebooting, second one reinstall marshmallow, upgrade to nougat, happened the same reboots, I made again a factory reset and now no reboots and way better battery life) everything is ok for now.
hekermeker said:
I have a thread about this, it was unusual for me too, theese random reboots.
After the third reinstall, (first one everyday rebooting, second one reinstall marshmallow, upgrade to nougat, happened the same reboots, I made again a factory reset and now no reboots and way better battery life) everything is ok for now.
Click to expand...
Click to collapse
Thank you for your reply I received the update in OTA. To reinstall I have to go through Odin? I can not simply reinstall the current firmware (Nougat) via Smart Swith for PC?
I have the same issue guys even if did an hard reset after nougat update. I experienced some reboots after the update (1 March) but very often in these last days. I enabled the pin code for the sim in this way we can see if it happens when don't "monitor" the phone.
I was getting random reboots at one point due to a kernel panic (something to do with Samsung's zswap implementation). It hasn't been happening for a while though. I think they probably fixed it in newer versions. I'm on DQCF currently.
rikiko1g said:
I have the same issue guys even if did an hard reset after nougat update. I experienced some reboots after the update (1 March) but very often in these last days. I enabled the pin code for the sim in this way we can see if it happens when don't "monitor" the phone.
Click to expand...
Click to collapse
I think this is a software bug. Hopefully Samsung will quickly realize and deploy a corrective update. For my part, I reported this problem by sending an error report via the application "Samsung Members".
CurtisMJ said:
I was getting random reboots at one point due to a kernel panic (something to do with Samsung's zswap implementation). It hasn't been happening for a while though. I think they probably fixed it in newer versions. I'm on DQCF currently.
Click to expand...
Click to collapse
I'm on DQBO, this may be why I still have this problem. Did you directly receive Android Nougant in DQCF or was it a patch update?
GeekTN said:
I'm on DQBO, this may be why I still have this problem. Did you directly receive Android Nougant in DQCF or was it a patch update?
Click to expand...
Click to collapse
Flashed full image from SamMobile and setup from scratch. I'm too impatient to wait for patches
having random freeze / reboot on a g930fd (dual sim) as well , since a few weeks
flashed several times, factory reseted several times, root or no-root ....
no solution ...
basile said:
having random freeze / reboot on a g930fd (dual sim) as well , since a few weeks
flashed several times, factory reseted several times, root or no-root ....
no solution ...
Click to expand...
Click to collapse
This may be a software bug. What is your firmware version?
build NRD90M G930FXXU1DQB7 is the latest rom
with the latest samsung security update
meanwhile I left root aside, as I noted a strange thing while working under twrp that being 'unable to mount' /data map
problem occurs after filling up the memory (yes a 32gb version) and making more and more apps working (under root)
so, considering the above, might it be a physical ram problem ?
reading searching the net I noticed that many people are having this problem
basile said:
build NRD90M G930FXXU1DQB7 is the latest rom
with the latest samsung security update
meanwhile I left root aside, as I noted a strange thing while working under twrp that being 'unable to mount' /data map
problem occurs after filling up the memory (yes a 32gb version) and making more and more apps working (under root)
so, considering the above, might it be a physical ram problem ?
reading searching the net I noticed that many people are having this problem
Click to expand...
Click to collapse
No, I do not think that's what caused the problem. If the problem appeared after the Andoid Nougat update, it is that it is a software bug. I have a Galaxy S7 duos (SM-G930FD) me too and my firmware version is the G930FXXU1DQBO and I also have a problem of random restarts that persists even after a factory reset. Apperently the latest firmwares do not have this problem. It is necessary to wait for the next corrective update. Otherwise, what is the frequency of the random reboots of your phone? My phone is once a week.
there is no linearity ... can happen once a day, a week or several times in one day
sometimes it completely gets stuck and I have to wait for the battery to fully discharge before being able to reboot to a working phone ...
basile said:
there is no linearity ... can happen once a day, a week or several times in one day
sometimes it completely gets stuck and I have to wait for the battery to fully discharge before being able to reboot to a working phone ...
Click to expand...
Click to collapse
Have you tried restarting your phone in secure mode to see if the problem is from an application that you have installed?
Same here, I though that was Fleksy that sometimes load the phone and I had to shut it down manually (Power button + volume - for 7 sec) for a restart. Sometimes it restart itself.
Very frustrating, I'm on G930FXXU1DQB1 (German model), and when i search for update it says "up to date : DQB3 / DQA8 / DQB1."
Irritating as well !
Greg2Lu said:
Same here, I though that was Fleksy that sometimes load the phone and I had to shut it down manually (Power button + volume - for 7 sec) for a restart. Sometimes it restart itself.
Very frustrating, I'm on G930FXXU1DQB1 (German model), and when i search for update it says "up to date : DQB3 / DQA8 / DQB1."
Irritating as well !
Click to expand...
Click to collapse
This problem of random reboots often happens to your phone? What is the frequency of these restarts?
Since a couple of days my Samsung Galaxy S6 SM-G920F keeps to restart randomly or even just power off.
It started rarely and now it does it even every few minutes.
Sometimes it just restart suddenly other times it freezes for some seconds and then restart.
It seems an hardware issue because the problem persists even after a factory reset.
Do you think about anything I could try before I give up?
I could try to flash a previous firmware (current is G920FXXU5EQH1) but the problem started some days after the last OTA update.
You can try reflash latest stock (HERE you found all), but looks like hardware issue... Were there any heavier falls or contact with water?
rifek4 said:
You can try reflash latest stock (HERE you found all), but looks like hardware issue... Were there any heavier falls or contact with water?
Click to expand...
Click to collapse
No, no fall or contact with water.
I'm downloading the previous stock and I'll try it just to eliminate the doubt that could be the latest firmware instead.
But I agree that it looks like an hardware issue but, which part? Could it be the motherboard?
The randomness of the restart make me think of a NAND or ram issue. What's your opinion please?
ian.ex said:
No, no fall or contact with water.
I'm downloading the previous stock and I'll try it just to eliminate the doubt that could be the latest firmware instead.
But I agree that it looks like an hardware issue but, which part? Could it be the motherboard?
The randomness of the restart make me think of a NAND or ram issue. What's your opinion please?
Click to expand...
Click to collapse
Don't try flash previous stock just like latest because there can be problems with bootloader etc and won't start. Just try latest stock downloaded via SamFire flashed via latest Odin3 with latest drivers.
Most often the eMMC is damaged for unknown reasons, it's on mobo.
rifek4 said:
Don't try flash previous stock just like latest because there can be problems with bootloader etc and won't start. Just try latest stock downloaded via SamFire flashed via latest Odin3 with latest drivers.
Click to expand...
Click to collapse
I flashed last firmware G920FXXU5EQH1 with odin that said "PASS!". Then S6 rebooted in recovery saying "Installing update", after some second saying "Erasing" then rebooted and now is in "No command" state.
I don't know what to do at this point. Since the flash went ok maybe it's not a NAND problem.
Any other idea?
nvm, after installing TWRP the S6 freezes even using TWRP and this is a confirmation that it's an hardware issue.
ian.ex said:
I flashed last firmware G920FXXU5EQH1 with odin that said "PASS!". Then S6 rebooted in recovery saying "Installing update", after some second saying "Erasing" then rebooted and now is in "No command" state.
I don't know what to do at this point. Since the flash went ok maybe it's not a NAND problem.
Any other idea?
Click to expand...
Click to collapse
When you see 'no command' when you try get in to stock recovery, use both Volume button's or Home to get the menu options. You should see that after few clicks
rifek4 said:
When you see 'no command' when you try get in to stock recovery, use both Volume button's or Home to get the menu options. You should see that after few clicks
Click to expand...
Click to collapse
I did bring the S6 to a technician and he said that it's the internal memory and I have to replace the motherboard.
I found some at 45€/60€ for the G920F but is there something that I should pay attention like IMEI or other things?
ian.ex said:
I did bring the S6 to a technician and he said that it's the internal memory and I have to replace the motherboard.
I found some at 45€/60€ for the G920F but is there something that I should pay attention like IMEI or other things?
Click to expand...
Click to collapse
Yes, exactly what I told NAND/memory in S6 case is eMMC, and mainly that is broken from unknown reasons. Some S6 are more sensitive and one fall down can makes broken eMMC But ~50-60€ isn't bad price for mobo. You will be have just new IMEI etc ofcourse. Just be sure you buying from good source, and all will be 100% working and not from stolen phone
So I've "successfully" updated to v8.0 using the above method. I'm currently on build 2CQL1. I updated from AQH7 to 2BQJA and then to CRA4 using the Samsung Firmware Science downloads. My phone is stock AT&T (not unlocked), and is not rooted. When going to CRA4, I encountered a pretty significant error which continues to plague me. I've searched through the forums and haven't read anything on similar to this issue. I cannot use Always on Display. It has to be turned off, and..I cannot take the update in Google play for the Always on Display app. If I try and take the update, the phone goes into this weird state: Screen dark except for the edge indicator. Phone will vibrate three times, but screen will remain dark. Only options I have is to try and restart or turn off. I was able to get into the recovery menu, and do a reset to factory settings. However, upon doing that I noticed that I was running build 2CQL1. After doing this a couple of times, I finally figured it out it was the AOD that was giving me issues. So I disabled it in the phone settings, and will not take the update in Google Play.
Update: Now, I'm getting the vibrations randomly, even with AOD turned off. The phone is still functional, but I fear I may have to reboot and do a reset at any moment.
Anybody have any thoughts on how I can get back to a stock version of ATT software? Again, I don't need to root or even unlock my phone. Just looking for the stock software so I can have a functional device.
Thanks in advance
Lavman72 said:
So I've "successfully" updated to v8.0 using the above method. I'm currently on build 2CQL1. I updated from AQH7 to 2BQJA and then to CRA4 using the Samsung Firmware Science downloads. My phone is stock AT&T (not unlocked), and is not rooted. When going to CRA4, I encountered a pretty significant error which continues to plague me. I've searched through the forums and haven't read anything on similar to this issue. I cannot use Always on Display. It has to be turned off, and..I cannot take the update in Google play for the Always on Display app. If I try and take the update, the phone goes into this weird state: Screen dark except for the edge indicator. Phone will vibrate three times, but screen will remain dark. Only options I have is to try and restart or turn off. I was able to get into the recovery menu, and do a reset to factory settings. However, upon doing that I noticed that I was running build 2CQL1. After doing this a couple of times, I finally figured it out it was the AOD that was giving me issues. So I disabled it in the phone settings, and will not take the update in Google Play.
Update: Now, I'm getting the vibrations randomly, even with AOD turned off. The phone is still functional, but I fear I may have to reboot and do a reset at any moment.
Anybody have any thoughts on how I can get back to a stock version of ATT software? Again, I don't need to root or even unlock my phone. Just looking for the stock software so I can have a functional device.
Thanks in advance
Click to expand...
Click to collapse
//N950U ATT\\ Stock Odin Files Firmware N950USQU3CRC2
https://r.tapatalk.com/shareLink?sh...ers.com/showthread.php?t=3783711&share_type=t
Sent from my iPhone using Tapatalk
jerrycoffman45 said:
//N950U ATT\\ Stock Odin Files Firmware N950USQU3CRC2
https://r.tapatalk.com/shareLink?sh...ers.com/showthread.php?t=3783711&share_type=t
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thank you for the response. Can I just download the .zip file to my phone's SD care from the link and install it from the Recovery menu?
Lavman72 said:
Thank you for the response. Can I just download the .zip file to my phone's SD care from the link and install it from the Recovery menu?
Click to expand...
Click to collapse
no you need a computer
This is all set. I downloaded the latest official AT&T update, and installed using ODIN. Thanks to everyone for the assistance. It had been a while since I had done anything like that. Back to the Samsung Infuse days.
The phone freezes and flickers
Reboots automatically at intervals for no reason at all
Did you have magisk installed?
FelipeHiroshi said:
Did you have magisk installed?
Click to expand...
Click to collapse
No. This happened right after the unboxing also. The screen pixelates and then rebooted. Til now the problem is there. But it's less frequent now. Please help me fix this
Uhum very weird try the easy first,factory reset and wipe cache,if din't work you can try flash another stock firmware via odin.
FelipeHiroshi said:
Uhum very weird try the easy first,factory reset and wipe cache,if din't work you can try flash another stock firmware via odin.
Click to expand...
Click to collapse
I already tried factory reset for like two times. Didn't help. Lemme try to flash another firmware and see if it resolves. Thanks
I also have the reboot issue. I don't have any other issues. My phone has the official firmware, I didn't flash any custom rom.
The problem first showed up for me a few days after the November firmware update.
MeDontWorry said:
I also have the reboot issue. I don't have any other issues. My phone has the official firmware, I didn't flash any custom rom.
The problem first showed up for me a few days after the November firmware update.
Click to expand...
Click to collapse
For me now all problems have subsided. I haven't encountered any problems since last week. I didn't even update. The problem just vanished. Thank goodness. Btw, keep an eye out for One UI 4 Android 12 update. It's fix most of the problems. And might bring new problems too lmao
Oh amazing!! I'm happy for you! I most certainly will, I'm looking forward to the update. The weirdness is that it only happens very occasionally! Like, in total I've encountered it less than 10 times I guess. It happened three days ago and again today (while I certainly use my phone a few hours a day).
MeDontWorry said:
Oh amazing!! I'm happy for you! I most certainly will, I'm looking forward to the update. The weirdness is that it only happens very occasionally! Like, in total I've encountered it less than 10 times I guess. It happened three days ago and again today (while I certainly use my phone a few hours a day).
Click to expand...
Click to collapse
Let's hope your phone also would get better soon. It's not like a software problem or anything. I don't know what kind of sorcery this is. Samsung must have put a spell on these phones
Haha thank you! I still hope that it's a random and weird software issue, so that it can be solved in the next update lol.