Related
Hi all, I'm new to XDA so hopefully someone can help me. I purchased a brand new unlocked note 3 N9000W8 in canada from a cellphone store on Monday Morning. The phone was great and worked without a hitch and had android 4.3 on it.
Later on during the day, there were numerous news headlines regarding a 4.4.2 was officially released. So i decided to do the software update. With failed attempts with the message "Your device have been modified, Software updates are not available"
I checked my Settings > about device > status > device status and it states custom or modified. I am unsure how this is possible thinking it was a brand new phone. After some in depth reading i powered off the phone and check the android download mode (power, home button vol down key combo).
It states device status: custom, firmware: custom, knox 0x1 (which meant my warranty was gone essentially). I proceeded to call the shop i purchased the phone at, and the manager said they buy the phones from the distributor which unlocks them before it gets in their hands. so it must have been rooted prior to me receiving the phone.
Long story short...i know its been quite the reading already my appologies. I used samsung KIES to backup the phone and it updated it back to the stock firmware 4.4.2. I was prepared to loose the root as i dont need it. More concerned about the warranty. With the device and firmware status back to original i can now do OTA updates, however
Problem i have now is after the factory firmware upgrade to stock, my sim no longer works on the network. Seems as if the device has a sim lock, but it never asked for one. A local cellphone shop in st.catharines said there might be an issue with the baseband after the official update.
before the update, i tried all the suggestions such as unmounting the sd card, wiping cache, using supersu to unroot.
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.
i just realized this was posted in the wrong section of the forum. sorry mods, can it be moved to Q/A?
tedmonddo said:
Hi all, I'm new to XDA so hopefully someone can help me. I purchased a brand new unlocked note 3 N9000W8 in canada from a cellphone store on Monday Morning. The phone was great and worked without a hitch and had android 4.3 on it.
Later on during the day, there were numerous news headlines regarding a 4.4.2 was officially released. So i decided to do the software update. With failed attempts with the message "Your device have been modified, Software updates are not available"
I checked my Settings > about device > status > device status and it states custom or modified. I am unsure how this is possible thinking it was a brand new phone. After some in depth reading i powered off the phone and check the android download mode (power, home button vol down key combo).
It states device status: custom, firmware: custom, knox 0x1 (which meant my warranty was gone essentially). I proceeded to call the shop i purchased the phone at, and the manager said they buy the phones from the distributor which unlocks them before it gets in their hands. so it must have been rooted prior to me receiving the phone.
Long story short...i know its been quite the reading already my appologies. I used samsung KIES to backup the phone and it updated it back to the stock firmware 4.4.2. I was prepared to loose the root as i dont need it. More concerned about the warranty. With the device and firmware status back to original i can now do OTA updates, however
Problem i have now is after the factory firmware upgrade to stock, my sim no longer works on the network. Seems as if the device has a sim lock, but it never asked for one. A local cellphone shop in st.catharines said there might be an issue with the baseband after the official update.
before the update, i tried all the suggestions such as unmounting the sd card, wiping cache, using supersu to unroot.
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.
Click to expand...
Click to collapse
When the distributor told you that the phone had been modified to enable an unlock, why did you say, "I was prepared to loose root as i dont need it"... the problem is fairly obvious, you had a software-unlocked phone and even though the seller told you that you would lose your unlock, you wiped it back to factory anyway lol...
honestly though, that's extremely sketch, lemme know that shop and I'll report them to BBB, you should never be paying for a cell phone that comes rooted unless your buying something from pacific mall, there are several options for you to unlock the phone, using software, hardware, or IMEI unlock codes
tedmonddo said:
...
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.
Click to expand...
Click to collapse
You had a pre-rooted software-unlocked phone (that was originally network-locked). Your warranty to Samsung is completely void, you should get something in writing (or record on audio) from the guy that sold you the phone as to the warranty of the phone.
Other than that - you can buy a network unlock code for something like 15 USD or so.
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Do you have memory card installed? if so then scan you memory card for possible viruses.
Actually I have this issue too before.
Even if I left it lying on the table, it can restart by itself.
I tried to update to latest PB1 rom, the update failed, the phone restart while ODIN updating.
So I use Kies recovery and got it working again.
After that, i tried again update to PB1 rom using ODIN. and now no issues at all.
I dont know which one did the trick whether update to PB1 or KIES recovery.
Goldendawn said:
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Click to expand...
Click to collapse
Munawar Mehmood said:
Do you have memory card installed? if so then scan you memory card for possible viruses.
Click to expand...
Click to collapse
Thanks - but no I don't - these are the first things I did when it started happening.
When it started happening I did factory reset, removing memory card, factory reset again, didn't restore backup from google... etc etc - so the general admin tech stuff.
Because under warranty (2 year contract) I didn't want to do anything more so sent to provider to get dealt with (into my 22 months of 24 months). For the last 4 months it has been to them a number of times for the same thing.
Now each time they send it back they claim "software corrupt" and that there is no hardware issue. So doing a software root and mod change for me is a hope - and probably not a good one - that the Stock 5.0 is the problem on this phone. And only going down this road because I am coming out of the warranty and right now I have a phone I can't really use, and damn Samsung won't support it or fix it (which is really all I want them to do!!) sigh
syamsoul said:
Actually I have this issue too before.
So I use Kies recovery and got it working again.
Click to expand...
Click to collapse
Thanks for this information, because in fact you are not the first time I have read this but I am not sure what the Kies recovery is - is there some instructions you have because maybe that is what should try, because I have seen other people on Google state this has helped them with restarting, but that was usually after Mod fix. Maybe there is something in the 5.0 update on GN3 that might cause this?
Rosli59564 said:
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Click to expand...
Click to collapse
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Goldendawn said:
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Click to expand...
Click to collapse
Just flash the firmware with odin. Factory reset in recovery after it's done. That's it. There are a lots of threads about going down such this:
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
I suggest you read through before you go further. They are mixed results. Some successful. Some did not. That is why it is better to flash the same csc firmware.
I even able to downgrade my S6 from 6.01 to 5.1.1 without issue but of course it's different phone.
Sent from my SM-N920C
---------- Post added at 08:38 PM ---------- Previous post was at 08:15 PM ----------
I sent you a PM.
Sent from my SM-N920C
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
So my gf bought herself a used S7 SM-G930A off eBay. I'm honestly unfamiliar with the S7 or the ROM scene as things apply to is so I'm coming into this at a disadvantage (I'm on an S5). However things don't seem quite right:
1) on the boot screen, there's an unlocked padlock icon with "Custom" under it
2) There's nothing for Software updates under About Device
3) Build number MMB29M.G930AUCS2APC2, Android Security patch level "February 1, 2016" (out of date?)
4) Repeatedly gets message: "Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes"
I checked some videos and I don't think this is a fake S7, but maybe it was rooted and/or had a custom ROM in a previous life. Honestly, if it's been rooted she really doesn't need that. I'd prefer to take it back to unrooted stock for her so she can have the normal consumer experience, getting carrier updates OTA, able to use Android/Samsung Pay, etc. Can anyone shed light on the state of things and guide me into getting her to where she needs to be? I'm ok running ODIN but am having trouble finding the latest stock ROM. Thanks.
(I apologize for not doing the normal amount of due diligence searching I'd normally do before pleading for assistance, but she's in a pickle now being phone-less until we can get this working).
The first thing you should do, if you haven't already, is check the IMEI.
https://swappa.com/esn
Many sellers on eBay buy cheaper phones and install the ATT rom. If it is a genuine att phone, you can restore it to stock by flashing software through Odin
Here is the latest post I found with the latest ATT software:
http://forum.xda-developers.com/att...are-g930aucs4api2-bootloader-4-t3481957/page2
This thread shows how to root and restore the galaxy s7:
http://forum.xda-developers.com/ver...s-root-install-xposed-unroot-t3411039/page206
Thanks, Luke. I just tried that link and the IMEI comes up clean and correct for the model.
As is my style, I didn't stop working on it after I posted that last night. I ultimately did find all the pieces for a stock re-flash, getting ODIN set up in a Windows 10 VM. It seemed to work, not only giving the phone a slightly newer firmware and security update, but fixing all the weirdness. So with any luck she's good to go. I suspect the phone was customized/hacked up a bit by the previous owner, and he didn't do a proper job returning it to 100% stock. Thank goodness she had someone like me who could fix it for her, otherwise an normal innocent buyer would've been in for a world of frustration and hassle.
This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
re: bootloops
whitebloodcell said:
This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Go into settings>developer's options and ENABLE OEM UNLOCK then
go into settings>general management>reset>factory data reset and
reset the phone.
Once you have done that the phone will work properly without rebooting
provided that you have successfully odin flashed the official samsung
G935F S7 Edge firmware prior to doing a factory data reset.
Good luck, have a great day!
Thanks for replying. Unfortunately I can't get into the phone at all. Only screen I have access to a recovery and downloader.
So I left the phone alone for a while and tried booting into safemode. This time it worked - sort of. It is asking me for a password, but I have never set one. I only ever set a pin and fingerprints. But since wiping everything that doesn't seem to apply anymore. What is the default password? I am referring to the phone password, rather than a google account obviously. I am not at that stage of the boot up.
Update: found the password (default_password), still boot looping on the optimising apps screen.
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
I have flashed stock rom (initially the version that matches my carrier, although my phone was bought sim free and unlocked, and then the version for unlocked phones (BTU in sammobile I think)) but it still just boot loops. The phone can remain in download mode as long as it wants, and previously, when it was asking for the password, it was able to remain on that screen indefinitely. I would have thought if it was a hardware problem the boot looping would happen regardless of the action on screen. Immediately after flashing the stock rom, it did start to load before ooting. Now it just boots immediately at the Samsung Logo.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
Just to be clear, do you mean repartition here? I have not checked that option before, will try it.
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
vsn4 said:
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
Click to expand...
Click to collapse
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
You can wipe your phone by entering recovery. Default recovery has the wipe option.
alehawk said:
You can wipe your phone by entering recovery. Default recovery has the wipe option.
Click to expand...
Click to collapse
Was the first thing I tried. Didn't help.
I got the bootloop thingy and was the cache, I wiped and the phone booted up
alehawk said:
I got the bootloop thingy and was the cache, I wiped and the phone booted up
Click to expand...
Click to collapse
Thanks for trying to help, but, again, already tried that.
whitebloodcell said:
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
Click to expand...
Click to collapse
Hope all goes well, let us know if you get it sorted out.
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
AnubuRe said:
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
Click to expand...
Click to collapse
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
whitebloodcell said:
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
Click to expand...
Click to collapse
For those perhaps in similar situation in the future, Samsung didn't care that it was purchased second hand, despite what the fine print says. They just looked at the serial number. In the course of trying my own repairs I flashed a custom rom, which of course tripped the knox warranty void bit. When I took it into the service centre they saw this and then wanted to charge £225 for an out of warranty repair. I refused at the time. I later called Samsung support and explained the situation (I said a phone repair shop must have done the flashing). Again on the phone I was told it would be an out of warranty repair, and this time I agreed. They collected my phone and returned it to me today however, with no invoice or mention of charges, so it looks like they just did the repair no questions asked.
I have the same issues, so far I'm getting by with flashing a stock rom with pit file and doing repartition and nand erase, normal cache/ factory reset doesn't help, it sometimes even boot loops while in twrp.
Somehow Odin flashing helps for a random amount of time, but it has thus far, crashed after a month, or a couple weeks since the last flash, etc. So far it's been my 5th boot loop event in the last 6 months
It sucks but as I got mine from another country (/win), didn't get the warranty ;( plus I tripped Knox by rooting.
sounds hardware related to me..
i had a friend with a note 4 who had similar problems it would hardly ever boot sometimes boot straight into download mode..
if by chance it did boot it would boot once the device was locked for a short time it would reboot and start over again bootlooping..
it was the emmc flash memory that was failing...
a workaround i found for this was the first thing i did when finally getting it to boot was install "Wake Lock - CPU Awake" and set it to never let the device sleep and to startup on boot...
this "fixed" it as long as your phone does not turn off... he had insurance though and sent it off and they sent him a new refirb
again this note 4 was untouched never rooted or anything
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
im having pretty much the exact same problem except ive been unsuccesful at flashing the stock firmware for my galaxy s7 active (SM-G891A). the active series isnt the most saute after, so finding the right firmware is alil more difficult. which im pretty sure is how i got into this situation! my question is what exacly does checking the "reparation" option do. i read to leave to leave it unchecked/unticked. maybe thats why ive been unsuccessful. and someone told me awhile ago not to fill in the "bt" box becuz i have a locked bootloader. this correct or no?