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
Related
Hi all,
My firmware has been the same since the day I bought it, which also was the day of release here in the UK, so it was 2.3.3. Today it said that a firmware upgrade was available, so I selected to download and install it. After a while it rebooted, showed it installing, then booted up normally. I got the main screen again and it said there were more software updates available, so I said to install those too. Again it rebooted, showed installation progress, then when booting up, it now gets permanently stuck on the boot screen where it just shows the Samsung Gaiaxy S II logo (along with the GT-I9100 text). I've left it for over 30 mins and nothing changes. I've tried rebooting several times, both with charging cable in and out, removed the battery for a few minutes and tried again, but it won't get beyond this screen anymore.
I looked at the thread about what to do about this situation (boot loop) which involved erasing user data, so I did this. The message that also came up during erasure said that it wiped the cache too. Tried rebooting after that but it's still stuck.
Is there a way to fix this?
Note that I've never installed custom firmware and never rooted my phone. I also don't have a 32-bit version of Windows, so can't use Odin (it never picks the device up). Plus I don't wish to void the warranty. Is it possible to get the official update zip package which I can flash from the recovery menu?
Thanks
Thom
Is there not a warranty provided by your cell carrier? I know in the us most carriers provide a 1 year warranty with all devices. They would exchange it gladly especially since you did everything by the rules.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
xijar said:
Is there not a warranty provided by your cell carrier? I know in the us most carriers provide a 1 year warranty with all devices. They would exchange it gladly especially since you did everything by the rules.
Click to expand...
Click to collapse
Yes, it's under standard warranty. I bought it sim-free without being tied to a network. I have already contacted Samsung and they said they'll email me details of the service centre to return it to, but I was hoping for a solution before needing to do that.
Nothing you can do without odin picking the phone up.
I use 64bit windows and it picks up fine, make sure you have the drivers installed (see the link in my sig, for my 4shared, where you can get them) or if you have kies installed you have them but make sure to kill all kies processes first in task manager.
But in the end, best bet is just to send it in, to make sure you dont void your warranty
Sorry this is a mistake.
darkixion said:
Hi all,
My firmware has been the same since the day I bought it, which also was the day of release here in the UK, so it was 2.3.3. Today it said that a firmware upgrade was available, so I selected to download and install it. After a while it rebooted, showed it installing, then booted up normally. I got the main screen again and it said there were more software updates available, so I said to install those too. Again it rebooted, showed installation progress, then when booting up, it now gets permanently stuck on the boot screen where it just shows the Samsung Gaiaxy S II logo (along with the GT-I9100 text). I've left it for over 30 mins and nothing changes. I've tried rebooting several times, both with charging cable in and out, removed the battery for a few minutes and tried again, but it won't get beyond this screen anymore.
I looked at the thread about what to do about this situation (boot loop) which involved erasing user data, so I did this. The message that also came up during erasure said that it wiped the cache too. Tried rebooting after that but it's still stuck.
Is there a way to fix this?
Note that I've never installed custom firmware and never rooted my phone. I also don't have a 32-bit version of Windows, so can't use Odin (it never picks the device up). Plus I don't wish to void the warranty. Is it possible to get the official update zip package which I can flash from the recovery menu?
Thanks
Thom
Click to expand...
Click to collapse
How did you erase user data?
Sent from my GT-I9100 using XDA Premium App
inkyadrian said:
How did you erase user data?
Click to expand...
Click to collapse
When it was switched off, I held down Vol-Up, Home and the power button. There was an option in the menu called "wipe data/factory reset". There's also a "wipe cache partition" option, the action of which is performed in the wipe data option anyway.
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..
KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..
KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday
And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was
My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated
Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.
Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:
Hello! My Galaxy Note 3 Exynos SM-N900 is now officialy a brick, so I guess this thread will help others to not do the same as I did. Here I go:
As you guys know, Exynos version of the Galaxy Note 3 doesn't have a lot of custom roms, so, I get tired of waiting for the kitkat update, donwloaded the Crisktelo rom 4.4.2, and flash it. Nothing wrong. The problem get with the camera, it works but takes so poor quality photos.
I tried to get back to stock, I get the Panama's TBA 4.4.2 stock firmware from Sammobile, because I am from Costa Rica and my Sammy is unlocked carrier free. Flashed as usual using Odin but the phone was the same no data was deleted, just the firmware changed. I wanted to get full wype to start again, backup everything and make factory reset using the menu on the phone. I totally forgot that the security option using Samsung Account to prevent theft was enabled. So I get to the screen of Samsung Account and get the ERR_0000 (Processing Failed) when I put my email and password for my Sammy Account. Aparently there is no way no get my phone back, this error is very weird in forums to happens and tried everything, from changing my password, by unsuscribing my account and enable it again. Flash the stock firmware several times, and as you know I can get the warranty because of the Know counter.
So maybe some of you are thinking to use that security feature, I guess if you use custom roms is a bad idea, but if you use stock there is no problem, even if your phone gets stolen, neither the thief or you can get it work again.
PS: I know ther is a thread similar to this one, but the difference is I KNOW my password and user, and this error is in the equation. So maybe I can get help or get help to others. Either way, I'm looking for a new phone, HTC One or LG G2?
As u can see Processing Error means -> wrong email/account has been entered.
Please use the correct account fro N900 otherwise u need to perfrom EFS clear
Also, can you check REACTIVATION LOCK in download mode and post result.
That is surely an expensive lesson. I guess Samsung Service Center can help you out providing that u can bring prove of purchase and be prepared for some financial charges as this kind of thing is surely out of warranty.
exprxp said:
As u can see Processing Error means -> wrong email/account has been entered.
Please use the correct account fro N900 otherwise u need to perfrom EFS clear
Also, can you check REACTIVATION LOCK in download mode and post result.
Click to expand...
Click to collapse
I read the whole thread but apparently is not available for end users just for Samsung Support... I think that is the solution but I can`t do it. But thanks!
nlatifolia said:
That is surely an expensive lesson. I guess Samsung Service Center can help you out providing that u can bring prove of purchase and be prepared for some financial charges as this kind of thing is surely out of warranty.
Click to expand...
Click to collapse
Indeed. My note 3 is just 3 months old, I have the invoice, I will send the phone this saturday to them, if they charge me more than $200 to do that I will let the phone as a loss and buy a new one. I'll update this thread.
JosHeron said:
Indeed. My note 3 is just 3 months old, I have the invoice, I will send the phone this saturday to them, if they charge me more than $200 to do that I will let the phone as a loss and buy a new one. I'll update this thread.
Click to expand...
Click to collapse
Noone will charge you.
JosHeron said:
Hello! My Galaxy Note 3 Exynos SM-N900 is now officialy a brick, so I guess this thread will help others to not do the same as I did. Here I go:
As you guys know, Exynos version of the Galaxy Note 3 doesn't have a lot of custom roms, so, I get tired of waiting for the kitkat update, donwloaded the Crisktelo rom 4.4.2, and flash it. Nothing wrong. The problem get with the camera, it works but takes so poor quality photos.
I tried to get back to stock, I get the Panama's TBA 4.4.2 stock firmware from Sammobile, because I am from Costa Rica and my Sammy is unlocked carrier free. Flashed as usual using Odin but the phone was the same no data was deleted, just the firmware changed. I wanted to get full wype to start again, backup everything and make factory reset using the menu on the phone. I totally forgot that the security option using Samsung Account to prevent theft was enabled. So I get to the screen of Samsung Account and get the ERR_0000 (Processing Failed) when I put my email and password for my Sammy Account. Aparently there is no way no get my phone back, this error is very weird in forums to happens and tried everything, from changing my password, by unsuscribing my account and enable it again. Flash the stock firmware several times, and as you know I can get the warranty because of the Know counter.
So maybe some of you are thinking to use that security feature, I guess if you use custom roms is a bad idea, but if you use stock there is no problem, even if your phone gets stolen, neither the thief or you can get it work again.
PS: I know ther is a thread similar to this one, but the difference is I KNOW my password and user, and this error is in the equation. So maybe I can get help or get help to others. Either way, I'm looking for a new phone, HTC One or LG G2?
Click to expand...
Click to collapse
You're not alone here, and I can tell you that this problem has absolutely nothing to do with the fact that you're using a custom rom, because my phone is on the stock 4.4 rom, and has never been rooted, wiped (until now), or tampered with.
This is not an "Expensive lesson," or a mistake on your part.
This is a broken feature of the note 3 device, and I have been on and off the phone with samsung all day.
So far there is nothing they can do from their end. And for those of you who are wondering, yes, you can log into your samsung account from your PC or whatever, but the activation lock will not let you in. I'm still working on resolving this issue. I think it's a problem with Samsung's login gateway to be honest. I experienced this last night at 10pm, and so far it hasn't been fixed.
So far I have this:
10pm - 7am EST: "Processing Failed.(ERR_0000)"
7am - 9am EST: "Unfortunately Samsung Login has stopped."
10am - 2pm EST: Processing failed
Between not letting me in and crashing, everything else has been pretty useless. Don't waste any more time formatting or wiping.
I CAN tell you that the minute I get back into the phone, I'm returning it to stock and putting it up for sale.
zer0xp said:
You're not alone here, and I can tell you that this problem has absolutely nothing to do with the fact that you're using a custom rom, because my phone is on the stock 4.4 rom, and has never been rooted, wiped (until now), or tampered with.
This is not an "Expensive lesson," or a mistake on your part.
This is a broken feature of the note 3 device, and I have been on and off the phone with samsung all day.
So far there is nothing they can do from their end. And for those of you who are wondering, yes, you can log into your samsung account from your PC or whatever, but the activation lock will not let you in. I'm still working on resolving this issue. I think it's a problem with Samsung's login gateway to be honest. I experienced this last night at 10pm, and so far it hasn't been fixed.
So far I have this:
10pm - 7am EST: "Processing Failed.(ERR_0000)"
7am - 9am EST: "Unfortunately Samsung Login has stopped."
10am - 2pm EST: Processing failed
Between not letting me in and crashing, everything else has been pretty useless. Don't waste any more time formatting or wiping.
I CAN tell you that the minute I get back into the phone, I'm returning it to stock and putting it up for sale.
Click to expand...
Click to collapse
Thanks! I try to spread this info to as many people as I can, Google+, Twitter, Facebook... People need to know that Samsung is doing this, and I know that this "feature" is not well implemented, I will go to the store and try to get a replacement. If Samsung is keeping this Knox and other security "fails" features, they are gonna keep me away from their products. Please keep updating if you get your device back working.
zer0xp said:
You're not alone here, and I can tell you that this problem has absolutely nothing to do with the fact that you're using a custom rom, because my phone is on the stock 4.4 rom, and has never been rooted, wiped (until now), or tampered with.
This is not an "Expensive lesson," or a mistake on your part.
This is a broken feature of the note 3 device, and I have been on and off the phone with samsung all day.
So far there is nothing they can do from their end. And for those of you who are wondering, yes, you can log into your samsung account from your PC or whatever, but the activation lock will not let you in. I'm still working on resolving this issue. I think it's a problem with Samsung's login gateway to be honest. I experienced this last night at 10pm, and so far it hasn't been fixed.
So far I have this:
10pm - 7am EST: "Processing Failed.(ERR_0000)"
7am - 9am EST: "Unfortunately Samsung Login has stopped."
10am - 2pm EST: Processing failed
Between not letting me in and crashing, everything else has been pretty useless. Don't waste any more time formatting or wiping.
I CAN tell you that the minute I get back into the phone, I'm returning it to stock and putting it up for sale.
Click to expand...
Click to collapse
I have had the exact same experience. A guy from tech support in the US said that mine may be trying to authenticate in the US, but since it is from Panama, it is conflicting and causing the error. He also mentioned a seemingly universal unlock code that can be provided from Samsung in the UK. I have already spent 10USD adding Skype credit in order to contact them, but they were closed when I called. I'm going to attempt it tomorrow. I will be destroyed if I have to send my phone to Panama or a similar place; the wait and customs can be aggravating.
The phone was so awesome (minus the volume warnings and skype vs call app default selection not working) before I upgraded to KitKat. I just wanted to factory reset it to make it stable :/
We should warn people not to select that Samsung Account option; it is certainly not stable.
lagoboss said:
I have had the exact same experience. A guy from tech support in the US said that mine may be trying to authenticate in the US, but since it is from Panama, it is conflicting and causing the error. He also mentioned a seemingly universal unlock code that can be provided from Samsung in the UK. I have already spent 10USD adding Skype credit in order to contact them, but they were closed when I called. I'm going to attempt it tomorrow. I will be destroyed if I have to send my phone to Panama or a similar place; the wait and customs can be aggravating.
The phone was so awesome (minus the volume warnings and skype vs call app default selection not working) before I upgraded to KitKat. I just wanted to factory reset it to make it stable :/
We should warn people not to select that Samsung Account option; it is certainly not stable.
Click to expand...
Click to collapse
Yeah, that's definitely not a bad idea.
If you find out anything about this "universal unlock code," be sure to post it here for the rest of us!
zer0xp said:
Yeah, that's definitely not a bad idea.
If you find out anything about this "universal unlock code," be sure to post it here for the rest of us!
Click to expand...
Click to collapse
Will do. If you can beat me to it, here is the "elevated tech support" number US: 1-888-987-4357 and this is the number in the UK that he gave me for the probable pipe dream code lol 4401932454358.
lagoboss said:
Will do. If you can beat me to it, here is the "elevated tech support" number US: 1-888-987-4357 and this is the number in the UK that he gave me for the probable pipe dream code lol 4401932454358.
Click to expand...
Click to collapse
I talk with the support in Panamá today. Because I Live in Costa Rica, I can call them for free. They didn't tell me anything about the universal unlock code. But only I have to take my phone back to the store and they will reset it. I Was wondering about what you say, how they can give you a unlock code even if they can't verify from distancie that you are the true owner of the phone?
I read in another thread here that Samsung support guys can only reset the phones verifying the true autenticy of the owner. If you wish, i can call samsung support in Panamá today and así if your phone using a firmware from Panamá needs to be sent there. I guess not but I can ask.
JosHeron said:
I talk with the support in Panamá today. Because I Live in Costa Rica, I can call them for free. They didn't tell me anything about the universal unlock code. But only I have to take my phone back to the store and they will reset it. I Was wondering about what you say, how they can give you a unlock code even if they can't verify from distancie that you are the true owner of the phone?
I read in another thread here that Samsung support guys can only reset the phones verifying the true autenticy of the owner. If you wish, i can call samsung support in Panamá today and así if your phone using a firmware from Panamá needs to be sent there. I guess not but I can ask.
Click to expand...
Click to collapse
That would be so helpful. Please ask them about it because my Spanish sucks lol. And please report back about the reset experience.
As far as that code, I admit that it does sound fishy like most things Sammy reps say. I thought they would investigate the processing failure instead of exploring the possibility that it wasnt really my phone.
I hope all goes well with resetting yours.
Sent from my XT560 using xda app-developers app
Thanks again JosHeron for offering to talk to Sammy in Panama for me.
I fixed my issue I used a XXUDNA9 4.4.2 KitKat rom that I flashed with ODIN 3.7. Once I flashed the rom, the phone rebooted and then it said that it was optimizing the apps. After that, I went through all of the steps and on the sign-in screen, it accepted my Sammy account and password on the first try.
Here is my theory on what caused the issue. When I did the recovery screen (vol up, home, power) wipe data and erase all, I think that it tripped the abnormal reset thing. Im not sure if it would do the processing failed if I had reset the phone from the settings menu. In any case, attempt to reinstall XXUDNA9 4.4.2 KitKat and then try to enter the Samsung account and Password.
Detailed Steps:
I am assuming that you have a SM-N900 International Note 3. If your phone does not boot with SM-N900 on the splash screen, find the appropriate stock rom for your phone. Otherwise, you can break your phone
This process should could take 4 hours +/- 1 depending on your internet speed.
Step 1: Get Materials (Adapted from http://nasirtech.blogspot.com/2014/02/n900xxudna9-android-442-kitkat-firmware.html)
- Download KitKat XXUDNA9 4.4.2 for SM-N900: http://terafile.co/3120933f433b
- Download Odin Verision 3.07 (3.09 does not play well with Note 3 and the old KitKat): https://copy.com/zowadQ32bn9T
Step 1: Factory Wipe and Clear Cache (Adapted from http://nasirtech.blogspot.com/2014/02/n900xxudna9-android-442-kitkat-firmware.html)
- Switch off the phone
- Remove the battery and then re-insert it after several seconds
- Next, press and hold simultaneously Volume Up, Home and Power.
- Release the buttons when the screen flickers and then wait for the Recovery Mode main screen to appear.
- If the Recovery Mode doesn’t boot, then you should keep trying until it does.
- Select factory wipe with the volume up key and then the power button, confirm
- Select Clear Cache
- Reboot the phone in normal mode by selecting the Reboot option.
Step 2: Make Sure the Phone to at least 80% capacity
Step 3: Reinstall KitKat XXUDNA9 (Adapted from http://nasirtech.blogspot.com/2014/02/n900xxudna9-android-442-kitkat-firmware.html)
- Switch off your phone and boot Galaxy Note 3 N900 into Download Mode by pressing and holding the Volume Down+Home+Power buttons (long press until the boot screen appear), now press Volume Up key to proceed to Download Mode.
- Extract the downloaded Odin3.07 zip file and run the Odin3 v3.07.exe file as an administrator (Right click on the .exe file and click on Run as administrator)
- Now connect your Galaxy Note 3 N900 to your computer via USB cable
- In Odin3 screen, you should see a COM Port number like “0:[COM7]” at ID:COM section and “Added!” text at the message box. This means -your device has been detected by Odin3.
- Make sure that, only the “Auto Reboot” and “F. Reset Time” options are checked. Failure to do so can brick (break/damage your device)
- Now, extract the downloaded firmware zip file, you’ll find a firmware file with extension .tar.md5
- In Odin screen, click on PDA button and select the firmware file with .tar.md5 extension (The firmware file look something like: N900XXDLJ5_N900ODDDLI7_INU.tar.md5)
- Now, click on the Start button to begin the installation process, wait few moments.
- Once completed, you would see “PASS!” message in ID:COM port having green background
- Your phone should automatically reboot after completion
- You can now disconnect your phone from computer
You should be able to enter your Samsung Account and Password without processing error_0000 now.
(Update: There is an issue with the Internet browser, flash the latest KitKat to fix)
Although it is fixed, I'm still scared about what else Samsung and Knox may do. I love the phone, but the thought of $700.00 down the drain was pretty horrific.
Lessons learned: Turn off that Samsung Activation thing before reset and don't update the phone until most users say that it is stable.
I hope this helps. I'm going to get some sleep. I've spent the night obsessing over it lol
lagoboss said:
Thanks again JosHeron for offering to talk to Sammy in Panama for me.
I fixed my issue I used a XXUDNA9 4.4.2 KitKat rom that I flashed with ODIN 3.7. Once I flashed the rom, the phone rebooted and then it said that it was optimizing the apps. After that, I went through all of the steps and on the sign-in screen, it accepted my Sammy account and password on the first try.
Here is my theory on what caused the issue. When I did the recovery screen (vol up, home, power) wipe data and erase all, I think that it tripped the abnormal reset thing. Im not sure if it would do the processing failed if I had reset the phone from the settings menu. In any case, attempt to reinstall XXUDNA9 4.4.2 KitKat and then try to enter the Samsung account and Password.
(Update: Email, the default Samsung app may crash. In order to fix, navigate to settings-> application manager -> Email -> and then force stop. Next clear the cache.)
Although it is fixed, I'm still scared about what else Samsung and Knox may do. I love the phone, but the thought of $700.00 down the drain was pretty horrific.
Lessons learned: Turn off that Samsung Activation thing before reset and don't update the phone until most users say that it is stable.
I hope this helps. I'm going to get some sleep. I've spent the night obsessing over it lol
Click to expand...
Click to collapse
It really does give me great pleasure to announce that this method worked for me as well. I'm gonna go out on a limb and say that the rough, official fix for this issue is as follows: (you'll get more detailed instructions on flashing and using Odin elsewhere, typing this quickly at work)
1) Download XXUDNA9 4.4.2 firmware for the SM-N900
2) Download Odin 3.07 (it is reported that the note 3 doesn't play well with 3.09)
3) connect your phone to your pc, open Odin and select your md5 file under PDA
4) allow it to complete the flashing process and then log into your Samsung account
Thanks to everyone who helped in trying to figure this out. I'm gonna check back and make sure everyone's phone was fixed.
Good luck!
lagoboss said:
Thanks again JosHeron for offering to talk to Sammy in Panama for me.
I fixed my issue I used a XXUDNA9 4.4.2 KitKat rom that I flashed with ODIN 3.7. Once I flashed the rom, the phone rebooted and then it said that it was optimizing the apps. After that, I went through all of the steps and on the sign-in screen, it accepted my Sammy account and password on the first try.
Here is my theory on what caused the issue. When I did the recovery screen (vol up, home, power) wipe data and erase all, I think that it tripped the abnormal reset thing. Im not sure if it would do the processing failed if I had reset the phone from the settings menu. In any case, attempt to reinstall XXUDNA9 4.4.2 KitKat and then try to enter the Samsung account and Password.
(Update: Email, the default Samsung app may crash. In order to fix, navigate to settings-> application manager -> Email -> and then force stop. Next clear the cache.)
Although it is fixed, I'm still scared about what else Samsung and Knox may do. I love the phone, but the thought of $700.00 down the drain was pretty horrific.
Lessons learned: Turn off that Samsung Activation thing before reset and don't update the phone until most users say that it is stable.
I hope this helps. I'm going to get some sleep. I've spent the night obsessing over it lol
Click to expand...
Click to collapse
Well, finally I can join and tell that my phone is back and running as before. Thank you guys, this method is the real fix for this issue and as always, I can find better support here than the official one.
7 days without the phone was horrible, because I had to use a laggy, crashed screen iPhone 4 with those little keyboards. God, no. I repeat Thank you!
JosHeron said:
Well, finally I can join and tell that my phone is back and running as before. Thank you guys, this method is the real fix for this issue and as always, I can find better support here than the official one.
7 days without the phone was horrible, because I had to use a laggy, crashed screen iPhone 4 with those little keyboards. God, no. I repeat Thank you!
Click to expand...
Click to collapse
I had the same problem, but after doing the procedure described before is working as well, I must say thank you to give us a solution, everything is working as before with my phone. thanks again.
I know this is off topic, but do you guys know of a real backup without root? After I reinstalled kitkat and restored the backup, I was not impressed; Kies is a joke
Sent from my SM-N900 using xda app-developers app
lagoboss said:
I know this is off topic, but do you guys know of a real backup without root? After I reinstalled kitkat and restored the backup, I was not impressed; Kies is a joke
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
I never do a "real" backup, I just backup my photos on OneDrive, Dropbox and Google+. My sms and whatsapp chats always get lost and the others like Telegram have sync. But do you ever tried Helium?
JosHeron said:
I never do a "real" backup, I just backup my photos on OneDrive, Dropbox and Google+. My sms and whatsapp chats always get lost and the others like Telegram have sync. But do you ever tried Helium?
Click to expand...
Click to collapse
Helium looks like it could work. I lost my subway surfer progress after I fixed the phone. With kies, it only saved text messages, photos and music, and some other useless settings. I think I may have backed up incorrectly with kies. When I selected apps, I don't think all of them were actually selected.
Anyhow, I'm definitely going to try helium. Some people in the comments said that it backed up the kind of data that I'm interested in.
Thanks.
Sent from my SM-P600 using xda app-developers app
I officially cannot get Wifi to enable. I try to enable it and it says "connecting" then turns back off..... I am current on firmware. Help?!
bigbad614 said:
I officially cannot get Wifi to enable. I try to enable it and it says "connecting" then turns back off..... I am current on firmware. Help?!
Click to expand...
Click to collapse
Now...after factory reset, to factory reset....WiFi still does not work, but my binary in bootloader keeps switching to "Custom" and after a while, it Device Status changes from "Official" to "Custom" under settings-->status....
Maybe the June update is the issue? I canceled my insurance on this line....think sprint will still take care of it?
Sprint is replacing the phone.
I now know of someone that has T-Mobile with an S7, never rooted; now is showing as Custom...Anyone else running the current security release that is having this issue?
There has to be someone.....
bigbad614 said:
I now know of someone that has T-Mobile with an S7, never rooted; now is showing as Custom...Anyone else running the current security release that is having this issue?
There has to be someone.....
Click to expand...
Click to collapse
Disabling apps can cause the device to say custom. My Verizon S7 has said custom pretty much since day 1, way before root lol. Have you rooted your phone? If so, there is a fix for the WiFi problem.
No apps were disabled; no root on this device, ever. Device has now been replaced by Sprint.
Hi, after going through the process of getting the S7 fixed - and Samsung denying everything (as usual), I'd share this issue as it's been happening to multiple Samsung devices in the workplace.
Here's how to brick your phone:
-An unwilling user goes on a business network, which happens to issue Android security updates via "Android at work".
-Due to Samsung making changes to Android, it manages to break the OS.
-Enjoy a chance to either go into infinite bootloops or if you're lucky - it'll boot in an unresponsive state with a line near the top and an empty desktop.
Now get this, because we tried to flash official firmwares provided by sammobile, the software state has been changed to custom. While the "warranty void" flag remains 0, they claim the device was rooted and want to charge ~$900 for it to be fixed.
As an owner of a S4 a few years ago, who's battery exploded. (And gave me a document to sign to not tell anyone about this) A note 5 owner who's display died while overseas and Samsung refusing to repair, as it wasn't bought in the US. I do not trust Samsung to make a reliable device.
Maybe your work security updates need updating / fixing
And flashing stock with ODIN does not change status to custom, as it is a stock ROM - in fact if your status is already custom and you use ODIN to flash stock, it will change back to Official
have you tried to reflash with odin?
oplix said:
have you tried to reflash with odin?
Click to expand...
Click to collapse
I also got a custom status once flashing samsung firmware, but that was only because the flash was terminated before completion.
Knox flag was still not triggered.
Flashed again with the same stock and now all was fine.
Showed back as Official.
I think you should try to use SmartSwitch if you want to go back to the original firmware, tho it comes with a cost of resetting the whole device including internal storage, you could boot into safe mode, copy your data, then open SmartSwitch > More > Emergency Initialization (or something like that) > 2nd Tab > you put the device model then Search > you put the S/N (check the back of the phone for S7, or under the battery for some phones) > follow the exact instructions > it will be initialized with the latest software and good as new. Hope this helps, also everybody knows Samsung likes not to be responsible on something they did, that's why xda and the devs here exist!
Turbine1991 said:
Hi, after going through the process of getting the S7 fixed - and Samsung denying everything (as usual), I'd share this issue as it's been happening to multiple Samsung devices in the workplace.
Here's how to brick your phone:
-An unwilling user goes on a business network, which happens to issue Android security updates via "Android at work".
-Due to Samsung making changes to Android, it manages to break the OS.
-Enjoy a chance to either go into infinite bootloops or if you're lucky - it'll boot in an unresponsive state with a line near the top and an empty desktop.
Now get this, because we tried to flash official firmwares provided by sammobile, the software state has been changed to custom. While the "warranty void" flag remains 0, they claim the device was rooted and want to charge ~$900 for it to be fixed.
As an owner of a S4 a few years ago, who's battery exploded. (And gave me a document to sign to not tell anyone about this) A note 5 owner who's display died while overseas and Samsung refusing to repair, as it wasn't bought in the US. I do not trust Samsung to make a reliable device.
Click to expand...
Click to collapse
I hope you learned a lesson and you will stop buying Samsung products so we dont have to read your pathetic posts(lies) ever again.