Ok; as a disclaimer, I am a long-time Rooter. For the record, I have not rooted since I had my Note 3; since then I have had a Note 4 and now an S7 Edge. This Sunday, after I had taken Sprint's newest security release (Sprint = PF2) I noticed that my WiFi would not enable. If you enabled it, it would say it was connecting, but then it would just switch back off. I started to dig into what was going on. I then rebooted into recovery...only to see that my binary was CUSTOM....Knox was/is not tripped. I then restart the phone to find in settings that my phone is no longer listed as official, it is now CUSTOM. Now I irritatedly factory reset my phone from settings. All is now clean and OFFICIAL. I try to enable Wifi, nope, it will not turn on. I then restart into recovery to find my device is now CUSTOM again....Rinse and repeat. I then do a factory reset from recovery...same failed result after a restart of the phone. Sprint failed to resolve (I have a replacement coming) and the Samsung REP at Best Buy was flabbergasted. The Samsung REP worked his magic only to realize that his magic did not resolve the issue either. I do not have HummingBad; scans have proven negative, in addition to a factory restart resolving that virus (even if I had it).
Now I find out that a friend of mine's--Sister-in-Law has an S7 with T-Mobile having the same CUSTOM Rom issue; although she is not having the WiFi issue.
This has got to do with the phone/version of Android.
What are everyone's thoughts?
Thank you for reading;
Nick
bigbad614 said:
Ok; as a disclaimer, I am a long-time Rooter. For the record, I have not rooted since I had my Note 3; since then I have had a Note 4 and now an S7 Edge. This Sunday, after I had taken Sprint's newest security release (Sprint = PF2) I noticed that my WiFi would not enable. If you enabled it, it would say it was connecting, but then it would just switch back off. I started to dig into what was going on. I then rebooted into recovery...only to see that my binary was CUSTOM....Knox was/is not tripped. I then restart the phone to find in settings that my phone is no longer listed as official, it is now CUSTOM. Now I irritatedly factory reset my phone from settings. All is now clean and OFFICIAL. I try to enable Wifi, nope, it will not turn on. I then restart into recovery to find my device is now CUSTOM again....Rinse and repeat. I then do a factory reset from recovery...same failed result after a restart of the phone. Sprint failed to resolve (I have a replacement coming) and the Samsung REP at Best Buy was flabbergasted. The Samsung REP worked his magic only to realize that his magic did not resolve the issue either. I do not have HummingBad; scans have proven negative, in addition to a factory restart resolving that virus (even if I had it).
Now I find out that a friend of mine's--Sister-in-Law has an S7 with T-Mobile having the same CUSTOM Rom issue; although she is not having the WiFi issue.
This has got to do with the phone/version of Android.
What are everyone's thoughts?
Thank you for reading;
Nick
Click to expand...
Click to collapse
That's strange, I've never seen or experienced that before in all my time of owning samsung devices. Did you try wiping everything from the recovery menu and then reflashing your stock firmware with odin?
I am with you on the "never seen or experienced that before in all my time owning Android devices." I have been running Android since the Evo. I wiped with recovery and let it rebuild on its own, I wiped from settings and let it rebuild, I flashed in Odin, Sprint did their magic wipe, Samsung did their magic wipe...in all of the cases, the phone boots up as Official and recovery shows Official. Once the phone restarts, the loop of CUSTOM starts....
I am totally baffled. It bothers me that my replacement might be refurbished...on top of that, I think it could happen again.
S7 Edge is custom after Samsung update
My phone just got an update yesterday and I let it update overnight/reboot.
After the update my stock/never rooted device is now also custom and I'm blocked from checking for system updates. I do not have the wifi issues, this is the T-Mobile variant.
I have emailed Samsung as I purposely avoided modifying this phone and now I don't want their accidental triggering of 'custom' to block my ability to have the phone maintained.
Samsung's terrible online chat team is of no use, I reached them after the email above received a "we don't support custom roms" when I clearly stated it was not rooted and not modified. So went to online chat and I'm told "it's rooted, because it says custom" - thanks for calling me a liar cheap front line support.
Then I'm told it's a custom rom because the baseband is not matching their database! That's funny I found the baseband as a release from July 10th as official.
http://pdadb.net/index.php?m=reposi..._s7_edge_android_6.0.1_system_update_uvu3apg1
Not a happy consumer right now.
wowwashington said:
"we don't support custom roms" .
Click to expand...
Click to collapse
If your S7E came from Sprint and has a Sprint ROM, AFAIK Samsung generally doesn't support "customized" (by operators) models directly.
As the ROM has been customized by Sprint, the baseband version is not present in the Samsung own database.
Therefore IMHO only the Sprint customer service could help you.
bigbad614 said:
Ok; as a disclaimer, I am a long-time Rooter. For the record, I have not rooted since I had my Note 3; since then I have had a Note 4 and now an S7 Edge. This Sunday, after I had taken Sprint's newest security release (Sprint = PF2) I noticed that my WiFi would not enable. If you enabled it, it would say it was connecting, but then it would just switch back off. I started to dig into what was going on. I then rebooted into recovery...only to see that my binary was CUSTOM....Knox was/is not tripped. I then restart the phone to find in settings that my phone is no longer listed as official, it is now CUSTOM. Now I irritatedly factory reset my phone from settings. All is now clean and OFFICIAL. I try to enable Wifi, nope, it will not turn on. I then restart into recovery to find my device is now CUSTOM again....Rinse and repeat. I then do a factory reset from recovery...same failed result after a restart of the phone. Sprint failed to resolve (I have a replacement coming) and the Samsung REP at Best Buy was flabbergasted. The Samsung REP worked his magic only to realize that his magic did not resolve the issue either. I do not have HummingBad; scans have proven negative, in addition to a factory restart resolving that virus (even if I had it).
Now I find out that a friend of mine's--Sister-in-Law has an S7 with T-Mobile having the same CUSTOM Rom issue; although she is not having the WiFi issue.
This has got to do with the phone/version of Android.
What are everyone's thoughts?
Thank you for reading;
Nick
Click to expand...
Click to collapse
Hi Nick. I have an s7edge. I am having the exact same issues. Exactly the same. My carrier is T-Mobile. I was wondering if you or if anyone has had any resolutions for this problem. I am totally Blown Away by what has been going on the last couple weeks for me with this issue. Thanks Keith G
That's really crazy ut seems new to me anyways I've learnt here
What happens when you search for OTA updates?
Do you get a message saying something like "Your device has been modified, no updates available"?
themissionimpossible said:
What happens when you search for OTA updates?
Do you get a message saying something like "Your device has been modified, no updates available"?
Click to expand...
Click to collapse
Here's what you get when you go to check for OTA - note, on my phone no other odd behavior is seen - other than device status = custom.
In this situation you'll likely never get new OTA updates...
I suspect that something went wrong during the latest T-Mobile OTA update...
If you are able to find the original T-Mobile ROM you might try to reflash your phone and start over.
themissionimpossible said:
In this situation you'll likely never get new OTA updates...
I suspect that something went wrong during the latest T-Mobile OTA update...
If you are able to find the original T-Mobile ROM you might try to reflash your phone and start over.
Click to expand...
Click to collapse
Samsung recommends that I take my phone to a Best Buy Samsung Experience location and have them flash over the OS - leaving the apps/data in place. I've yet to find a location that can do this.
---------- Post added at 12:00 PM ---------- Previous post was at 11:41 AM ----------
bigbad614 said:
Ok; as a disclaimer, I am a long-time Rooter. For the record, I have not rooted since I had my Note 3; since then I have had a Note 4 and now an S7 Edge. This Sunday, after I had taken Sprint's newest security release (Sprint = PF2) I noticed that my WiFi would not enable. If you enabled it, it would say it was connecting, but then it would just switch back off. I started to dig into what was going on. I then rebooted into recovery...only to see that my binary was CUSTOM....Knox was/is not tripped. I then restart the phone to find in settings that my phone is no longer listed as official, it is now CUSTOM. Now I irritatedly factory reset my phone from settings. All is now clean and OFFICIAL. I try to enable Wifi, nope, it will not turn on. I then restart into recovery to find my device is now CUSTOM again....Rinse and repeat. I then do a factory reset from recovery...same failed result after a restart of the phone. Sprint failed to resolve (I have a replacement coming) and the Samsung REP at Best Buy was flabbergasted. The Samsung REP worked his magic only to realize that his magic did not resolve the issue either. I do not have HummingBad; scans have proven negative, in addition to a factory restart resolving that virus (even if I had it).
Now I find out that a friend of mine's--Sister-in-Law has an S7 with T-Mobile having the same CUSTOM Rom issue; although she is not having the WiFi issue.
This has got to do with the phone/version of Android.
What are everyone's thoughts?
Thank you for reading;
Nick
Click to expand...
Click to collapse
Wow, after some wasted time with Samsung and trying to get help from their people at Best Buy. I stumbled across a potential fix!
Using old examples of the same 'suddenly custom' I found that the following put my S7 Edge back to 'Offical" after being custom for 3 days.
1) Power Off for 5+ seconds
2) Press and hold Volume Up and hit Power
3) Unlock icon/custom should be gone!
4) Release both buttons
5) Sign in
6) Settings/status/device status, this may be set at scanning for 45 seconds
themissionimpossible said:
What happens when you search for OTA updates?
Do you get a message saying something like "Your device has been modified, no updates available"?
Click to expand...
Click to collapse
My S7edge says that my device has been modified in an unauthorized way. Try using Smart Switch with your PC to manually download updates. ..... Keith G
Keith G said:
Try using Smart Switch with your PC to manually download updates. .....
Click to expand...
Click to collapse
It's always worth a try...
Keith G said:
My S7edge says that my device has been modified in an unauthorized way. Try using Smart Switch with your PC to manually download updates. ..... Keith G
Click to expand...
Click to collapse
Try what fixed my phone
1) Power Off for 5+ seconds
2) Press and hold Volume Up and hit/hold Power
3) Unlock icon/custom should be gone!
4) Release both buttons
5) Sign in
6) Settings/status/device status, this may be set at scanning for 45 seconds
Sprint has since replaced my phone and I updated straight to current and have had no issues for 8 days.
I had tried everything....this has been the only solution that stuck...
wowwashington said:
Try what fixed my phone
1) Power Off for 5+ seconds
2) Press and hold Volume Up and hit/hold Power
3) Unlock icon/custom should be gone!
4) Release both buttons
5) Sign in
6) Settings/status/device status, this may be set at scanning for 45 seconds
Click to expand...
Click to collapse
Could you explain those steps in a little more detail... Should I go into recovery for that... Thank you... Keith G
Sent from my Samsung Galaxy S7 Edge using XDA Labs
wowwashington said:
Try what fixed my phone
1) Power Off for 5+ seconds
2) Press and hold Volume Up and hit/hold Power
3) Unlock icon/custom should be gone!
4) Release both buttons
5) Sign in
6) Settings/status/device status, this may be set at scanning for 45 seconds
Click to expand...
Click to collapse
Thnx this has set my device status from custom to official.
I bought this s7 edge second handed en it came with a t-mobile boot logo. I flashed the BTU 7.0 update and it was set to custom.
Thank you because now i can install OTA updates again.
wowwashington said:
Wow, after some wasted time with Samsung and trying to get help from their people at Best Buy. I stumbled across a potential fix!
Using old examples of the same 'suddenly custom' I found that the following put my S7 Edge back to 'Offical" after being custom for 3 days.
1) Power Off for 5+ seconds
2) Press and hold Volume Up and hit Power
3) Unlock icon/custom should be gone!
4) Release both buttons
5) Sign in
6) Settings/status/device status, this may be set at scanning for 45 seconds
Click to expand...
Click to collapse
Thanks for this. These steps fixed my T-Mobile S7 Edge that was showing as custom. I have now installed the latest updates.
bigbad614 said:
Ok; as a disclaimer, I am a long-time Rooter. For the record, I have not rooted since I had my Note 3; since then I have had a Note 4 and now an S7 Edge. This Sunday, after I had taken Sprint's newest security release (Sprint = PF2) I noticed that my WiFi would not enable. If you enabled it, it would say it was connecting, but then it would just switch back off. I started to dig into what was going on. I then rebooted into recovery...only to see that my binary was CUSTOM....Knox was/is not tripped. I then restart the phone to find in settings that my phone is no longer listed as official, it is now CUSTOM. Now I irritatedly factory reset my phone from settings. All is now clean and OFFICIAL. I try to enable Wifi, nope, it will not turn on. I then restart into recovery to find my device is now CUSTOM again....Rinse and repeat. I then do a factory reset from recovery...same failed result after a restart of the phone. Sprint failed to resolve (I have a replacement coming) and the Samsung REP at Best Buy was flabbergasted. The Samsung REP worked his magic only to realize that his magic did not resolve the issue either. I do not have HummingBad; scans have proven negative, in addition to a factory restart resolving that virus (even if I had it).
Now I find out that a friend of mine's--Sister-in-Law has an S7 with T-Mobile having the same CUSTOM Rom issue; although she is not having the WiFi issue.
This has got to do with the phone/version of Android.
What are everyone's thoughts?
Thank you for reading;
Nick
Click to expand...
Click to collapse
My exact problem came from having something disabled in Packers Disabler Pro. I had the exact same issue with my device saying "custom" when in actuality it was Official. I'm with Tmobile as well. I took all the same steps to address the issue but nothing helped until I enabled all the apps that were disabled in Package Disabler Pro then restarted device. All was well. I carefully watched what I disabled in the future. I still do not know which app caused this but I take my time and check my device's status(official/custom) after disabling any apps.. Thank you... Keith G
I'm hoping to prevent my phone from taking updates in case a root exploit is found (but then quickly patched by VZ). I've disabled updates in the developer options (Settings/About Phone/Software Info/Build Number - click 7 times to enable developer options menu / developer options menu / Automatic system updates set to off).
I did that the other day and that was after taking the first "performance" OTA which had already downloaded/installed.
I figured that would do the trick however and hour ago I had my phone sitting on my desk connected to my PC via USB and when I picked it up there was a note saying something about my phone had been updated(?). Maybe it was just a notification I hadn't gotten from the first one somehow popping late but I'm kinda confused.. And this was a message about a system update (I should have screenshotted it or read it more my first thought was **** did I not toggle that developer option correctly....but I had). It was the message saying you may want to reboot as it may have drained the battery on your phone.
I'm on Software: VS99511A
Config: B16.LGE.VS995.0
Build NRD90M
Kernel [email protected]
I noticed in Application manager if I show system I can see 2 "System Updates" and I'm guess those are what kicked on and did something while I wasn't paying attention. Can those be disabled? One of them has an advanced permission for "Modify system settings" which I toggled to "no" cause I figured at worst that would just cause an error. The other I can only force stop and then disable but when I attempt to do that it warns me that doing so would hide it and I'm afraid I might not be able to relocate it/re-enable it (w/o a factory reset?) and that could be a serious problem
How is everyone else in the "hoping root come relatively soon" boat handling updates?
Thanks for any discussion/suggestions....
JayBTV said:
I'm hoping to prevent my phone from taking updates in case a root exploit is found (but then quickly patched by VZ). I've disabled updates in the developer options (Settings/About Phone/Software Info/Build Number - click 7 times to enable developer options menu / developer options menu / Automatic system updates set to off).
I did that the other day and that was after taking the first "performance" OTA which had already downloaded/installed.
I figured that would do the trick however and hour ago I had my phone sitting on my desk connected to my PC via USB and when I picked it up there was a note saying something about my phone had been updated(?). Maybe it was just a notification I hadn't gotten from the first one somehow popping late but I'm kinda confused.. And this was a message about a system update (I should have screenshotted it or read it more my first thought was **** did I not toggle that developer option correctly....but I had). It was the message saying you may want to reboot as it may have drained the battery on your phone.
I'm on Software: VS99511A
Config: B16.LGE.VS995.0
Build NRD90M
Kernel [email protected]
I noticed in Application manager if I show system I can see 2 "System Updates" and I'm guess those are what kicked on and did something while I wasn't paying attention. Can those be disabled? One of them has an advanced permission for "Modify system settings" which I toggled to "no" cause I figured at worst that would just cause an error. The other I can only force stop and then disable but when I attempt to do that it warns me that doing so would hide it and I'm afraid I might not be able to relocate it/re-enable it (w/o a factory reset?) and that could be a serious problem
How is everyone else in the "hoping root come relatively soon" boat handling updates?
Thanks for any discussion/suggestions....
Click to expand...
Click to collapse
In developer options there is disable automatic system updates. I like that feature.
Edit: sorry. I reread and saw you saw that. I had recently found that.
I'm still on 10b I disabled in the dev section and I get the constant you need to update but hasn't done it auto thankfully
Sent from my VS995 using Tapatalk
Any idea how to get past a at&t v20 that has updates already trying to install? Flash a new ROM or maybe a factory reset? BTW its already rooted but I forgot to disable the OTA updates. Thanks. EDIT: Nevermind. Just did a wipe on dalvik and cache, which took care of the problem.
Freezing System updates 1_15_10_0 and System updates 1_16_02_0 using Titanium Backup (this requires root), will stop those messages. It was nearly the same set of processes for the V10.
I've also seen a recommendation to freeze FOTA Update 7.0, and a method using the phone's hidden menu.
I'm not addressing rootless options since this message was posted a month and half before me2151's DirtySanta bootloader and root guide was released, that's no longer an issue.
I'm on 10m and recently rooted. I cannot find 1_15_10_0...I found the other file and successfully froze it. I've also frozen the FOTA Update. I tried accessing the hidden menu, but I get an error message. On 10m, is there a 1_15_10_0?
EDIT: Sorry for digging such a long-dead thread. Didn't see the more recent one that's also active.
Hey guys I know this is OT but is it true that the v20 from Verizon is unlocked and can work with any other sim?
Nexus 6p update 7.1.1 verificaton failed??? New to droid and not a developer I bought from pawn shop this summer. Showed software up to date and sim worked calls/data on cricket network. Phone running dirty unicorns? ROM? SuperSU? No clue DU? Read about Nexus/google sending monthly security patches/updates but nothing here since may,1 patch phone showed being done week before i bought the phone? Finally like 12/6?7? received a system update "7.1.1" day after they began rolling out to 6p's from what I think I maybe understand:/? So clicked on update which " fixes crucial bugs and improves stability and performance for your nexus 6p." 1270.1mb file "OK" starts the "downloading" showing as status bar slowly showing progress moving left to right. Half hour later+/- download completes "Verification failed" ??? Nothing updated goes back to update screen loops thru the process downloading 30+/- minutes or so then same " verification failed" Need help securing phone/personal data etc making it my own praying my privates life still private (besides google) and that I'm not owned!?! Hoped update would return me to factory settings along with my peace of mind but without verification maybe unicorns have a point:/
Suggest you follow this link... http://www.wugfresh.com/nrt/ The safest way to fix your issue. Seams you have custom rom in the phone, and you are trying to update with a factory rom. This website will help you get the phone back to a factory stock rom and from then on you will be able to get OTA updates without issues.
I just got an OTA update for Nougat (BTU) on my S7 edge.
68MB, small update, so I let it install
I've had Secure Startup enabled on my device all along, never had an issue, but after this latest update had finished installing, device rebooted, asking for my device pin as usual, but it will not accept my PIN! I've been very very very careful in entering the 4 digit device pin correctly, but it just won't verify! Please help, I'm desperate, have 4 attempts left before it resets the device!
My last reboot was about 2 or 3 days ago, same pin worked, but broken after the OTA update.. I don't want to factory reset if I can help it, haven't done a Smart Switch backup in about 2 months, so my app data will be well out of date if I do
So I eventually gave in and did a factory reset (no choice)
Samsung Cloud FTW - restored my apps, home screen settings (even folders and shortcuts) from the nightly cloud backup! All I missed was this morning's WhatsApp texts (also nightly backup to Google Drive - WhatsApp detected that backup without any prompting, awesome!)
So all that I lost in the end was a good chunk of my day (letting nearly 200 apps reinstall is a slow process, and then anything with TFA needed to be re-logged-in, and my code gen app for TFA reconfigured, but overall it was pretty painless, all considering!
AngelaRI said:
I just got an OTA update for Nougat (BTU) on my S7 edge.
68MB, small update, so I let it install
I've had Secure Startup enabled on my device all along, never had an issue, but after this latest update had finished installing, device rebooted, asking for my device pin as usual, but it will not accept my PIN! I've been very very very careful in entering the 4 digit device pin correctly, but it just won't verify! Please help, I'm desperate, have 4 attempts left before it resets the device!
My last reboot was about 2 or 3 days ago, same pin worked, but broken after the OTA update.. I don't want to factory reset if I can help it, haven't done a Smart Switch backup in about 2 months, so my app data will be well out of date if I do
Click to expand...
Click to collapse
Is anyone else having this issue?
What I read from the stock FW thread, if a firmware is flashed using odin (not OTA) there are a lot of comments to have Secure PIN enabled because a PIN is required afterwards?!
So what to do when updating with OTA? pin enable? disable?