After last update. - Samsung Galaxy S7 Edge Questions and Answers

After last update , new TouchWiz from s8 can't install . Before update she's working perfect. I tried to clean catch partition and nothing.
Please help me.

Same here. If you do factory reset and dont sign into your accounts it should let you install it.

clear the launcher data then try again

June update or May

Same problem after factory reset.

In 9 june receive firmware update.

Another problem.

Related

Problem since last update (Bell)

Hello all,
the S4 is my 4th Android cellphone and I also have a few more other Android devices.
Since the last update, I have a few apps that crash to to the main screen with no error message once in a while.
I NEVER had this problem with any of my current or previous Android devices (except the S4 with latest patch, it was fine before the patch btw).
So before I wipe the phone I wanted to know if it was a common problem with the S4 and the latest update.
Thanks.
Note: The phone is stock + CF Root, thats it.
not a common issue no: was your update OTA? First thing I would do is go into recovery and wipe the cache and the davlik cache and re-boot. If the problem persists, you may want to wipe the data -- it sounds to me that the issue is some remnant data from an app that needs updating to the latest firmware -- I presume you've gone into play store and updated all your apps since the OTA update of the firmware?

Unenrolled in N BETA program, never installed it, can't get notification removed

So I signed up for the ota preview, but then decided against installing it till a later build as a couple bugs I read about worry me.
I unenrolled, yet the notification still pops up, and its in system - updates.
I saw someone recommend wiping cache, so I booted in to recovery, and wiped, and its still there.
. I also tried deleted the catch of Google services.
Idea idea how to get rid of this? Ideally I'd like the new 6.0 ota that is coming and try that till the N OTA is more stable.
Had the same problem but in a different manner, when i decided to unenrolled the android beta page didnĀ“t gave me any device to do that, so what i did was, wiped my 6P, signed with a diferent user/email than mine, went to android beta page with that same user/email and the page then informes that 6P is on the N program, unenrolled, problem solved.

Android 7.0 OTA Google Play Services crashing

Hey guys,
Wanted to try and find out whether anyone else is experiencing issues with Google Play Services (9.4.52) crashing after upgrading to Nougat OTA?
I thought I may have a botched install so tried the following:
- Cleared cache
- Reset and didn't restore from backup
- Reset and only installed stock apps
- Safe mode
- Cleared Google Play Services data
- Unsubscribed from all Google beta testing apps
I still can't figure this one out, even after a hard reset back to stock it still kicks up a play services crash about once ever 10-20 minutes... very weird... and frustrating
Anyone else had this issue? Or got any suggestions?
I had the exact same problem after accepting OTA yesterday via the beta program. I was on 6.0.1 on my 6P (no root, no custom rom, locked boot-loader). All Google Apps and Services crash including Messenger (SMS). I performed a hard reset with no luck. I flashed OTA with no luck. Only solution was to unlock boot-loader, flash recovery, and go back to stock. I will try again today.
cybrdude said:
I had the exact same problem after accepting OTA yesterday via the beta program. I was on 6.0.1 on my 6P (no root, no custom rom, locked boot-loader). All Google Apps and Services crash including Messenger (SMS). I performed a hard reset with no luck. I flashed OTA with no luck. Only solution was to unlock boot-loader, flash recovery, and go back to stock. I will try again today.
Click to expand...
Click to collapse
Will try that method instead, the crashes have died down again but I can't find any correlation between specific apps and what's causing the crashes! If I find a solution I'll post.
I think there may be a problem with the final release. It seems Google pulled 7.0 from their factory images site. I downloaded 7.0 for nexus 6, 6P and 9 earlier today and only the download for the Nexus 9 is still available. I don't know which version is giving you a problem but on the Nexus 6P Google earlier posted version MTC20F. I was going to flash it this evening but I think I'll wait and see what version they post back to the factory image site.
Google has finally posted the OTA and Full ROM images for 7.0. Both have the exact same problem on my 6P. All Google Services and Apps crash and the phone reboots randomly (often). I am at a loss. Obviously issues exist with 7.0 and 6P. Google seriously needs to address this non-sense.

Updated my nougat and now my phone keeps rebooting after a minute of use

Hello. I have a Sprint s7e. Yesterday I updated my phone to the Nougat Beta and everything was going good. This morning I got a notification that an update was available so I accepted and it once it finished my phone keeps rebooting. It will fully load and within a minute of use, it will reboot. Even if I don't use the phone after the reboot, it will reboot in about a minute. Anyone else experiencing this? Possible fixes? I tried Safe Mode and it still rebooted. One mistake I made was I have items disabled with EZ Disabler which I forgot to re-enable. Ive done this before on Marshmallow and it never gave me any issues. Could this be the problem?
Is there a way to revert back to the older Beta Version, or even Marshmallow? Thanks
I would try a factory reset
Sent from my SM-G935P using Tapatalk
I would either try a factory reset or clearing the Cache. The last option would be a factory reset back to Marshmellow and then re-download the beta.
This happens on my wifes s7 edge. I assume its because of the (snapdragon 820) bootloader not liking root. Factory reset didnt solve issue for me because it threw up dm verity argument errors. Only thing that worked was flash combination firmware to completely wipe.
I had a similar issue. I would wipe data and clear cache. Start fresh. Android 7.0 vs 6.01 might have had compatibility issues or data corrupt caused bootloop. This is just my opinion. It sucks redoing everything, trust me. I had the Note 7 then got the s7 edge on Thursday, set it up on the stock 6.0.1. Then Friday found the Nougat beta and did my 1st download. It keeper rebooting constantly after It had finished set up.of course. So, I had to reset it up. I was able to go a day then reboot stuff happened again. So I data wiped and did it all over but this time I did not restore apps. I did fresh install and happy to report no issues thus far.
Sorry for long drawn out personal response, was just trying to share my experience in the event that it is useful to you.
Sent from my SM-G935P using Tapatalk
Has anyone had a problem with "Android Wear has stopped"? It started with the last update to PL3. I've tried clearing app cache and data as well as clearing cache from recovery. Hopefully the next update will fix it, but I've been wondering if anyone with a android watch has had a problem.

Galaxy s7 edge factory reset issue

Hello everyone
Today I factory reset my galaxy s7 edge and it did not turn up with android 6, instead I found it on android 8.0.0 with September 2019 security patch, I didn't update my phone after the reset, I did the factory reset from the settings menu "general management" factory data reset, I had to reset it cuz my storage was always full after I deleted everything from it, it was still full and when I check storage settings, device memory, I see "files" occupate 15 GB I tried diskusage app and cleaning cache apps and everything else but couldn't find them hidden files so I factory reset my device and it did go well since I ended up on android 8, what is the issue here ? Can someone please explain this to me please ? Thanks in advance
MiMDZ said:
Hello everyone
Today I factory reset my galaxy s7 edge and it did not turn up with android 6, instead I found it on android 8.0.0 with September 2019 security patch, I didn't update my phone after the reset, I did the factory reset from the settings menu "general management" factory data reset, I had to reset it cuz my storage was always full after I deleted everything from it, it was still full and when I check storage settings, device memory, I see "files" occupate 15 GB I tried diskusage app and cleaning cache apps and everything else but couldn't find them hidden files so I factory reset my device and it did go well since I ended up on android 8, what is the issue here ? Can someone please explain this to me please ? Thanks in advance
Click to expand...
Click to collapse
If ota update is enabled, he can download the update and store it and when you reset the device, he installed this update. This is the single most plausible explanation in this case.
Dark Stranger said:
If ota update is enabled, he can download the update and store it and when you reset the device, he installed this update. This is the single most plausible explanation in this case.
Click to expand...
Click to collapse
Thanks for explaining that to me i was so confused, so basically i can't go back to android 6, right ?
Dark Stranger said:
If ota update is enabled, he can download the update and store it and when you reset the device, he installed this update. This is the single most plausible explanation in this case.
Click to expand...
Click to collapse
Another thing that confuses me is why it chose September 2019 patch update and not another one?
is there anyway to go back to android 6 without flashing the phone? I mean just using the factory reset option and did anyone else get android 8 after factory reset his galaxy s7?
MiMDZ said:
Another thing that confuses me is why it chose September 2019 patch update and not another one?
is there anyway to go back to android 6 without flashing the phone? I mean just using the factory reset option and did anyone else get android 8 after factory reset his galaxy s7?
Click to expand...
Click to collapse
This was probably the most recent version that was stored on your device. Android 6 only custom roms of portals of other devices, because due to the bootloader block, you will not be able to install anything other than the stock version for your device.
Dark Stranger said:
This was probably the most recent version that was stored on your device. Android 6 only custom roms of portals of other devices, because due to the bootloader block, you will not be able to install anything other than the stock version for your device.
Click to expand...
Click to collapse
Thank you very much, much appreciated it ?

Categories

Resources