Database Users

GT-N8013 and German 4.1.1 update

Hello all,
I have the GT-N8013 (US Version), and decided I wanted to get Jelly Bean on it, since Samsung hasn't really said anything about an update for the USA.
I just flashed the German 4.1.1 ODIN last night as per this thread. I was under the impression this would not affect the binary counter or the firmware status. However, my binary count is now 2 (I've never flashed anything else), and the firmware status is Custom, rather than Samsung Official/Normal.
As such, I can no longer receive OTA updates for this device. I wanted to keep myself in a position where I could still get OTA updates one way or another.
I've seen things about changing the CSC, but I'm not sure I want to wipe the device, especially if I wouldn't be guaranteed to get OTA updates afterwards. (Or would it be guaranteed that OTAs would work if I changed the CSC to DBT...?)
What is the best course of action to get back to Samsung Official/Normal status (USA or German), or can it even be done?
(If I can't get back to Samsung Official, is there somewhere to download GT-N8010 German update.zip files, rather than the 1GB ODIN files?)
Thanks in advance for any help!

You'll need to root and then use TriangleAway to reset your counter. Then you can unroot and reflash official 4.1.1 from sammobile.com or just keep your root. Either way, you have to root to reset your counter. I recommend ExynosAbuse. As for OTA updates, you'll have to unroot and flash back to stock for that. To accomplish this, I recommend bypassing ODIN and using MobileODIN to flash, just in case the 8010 firmware is what tripped your counter to begin with... you know, cause you put it on an 8013.
Sent from my GT-N7100 using XDA Premium HD app

kornfan71 said:
Hello all,
I just flashed the German 4.1.1 ODIN last night. I was under the impression this would not affect the binary counter or the firmware status. However, my binary count is now 2
Click to expand...
Click to collapse
Strange - Mine didn't do that for 4.11 or 4.1.2. It only changed when I rooted it. How are you checking that the Binary count is 2?
kornfan71 said:
The firmware status is Custom, rather than Samsung Official/Normal.
As such, I can no longer receive OTA updates for this device. I wanted to keep myself in a position where I could still get OTA updates one way or another.
Click to expand...
Click to collapse
This will be because there is a mismatch between the devices CSC and the Firmware that is installed. You WILL lose all data if you wipe the device (Yes I've done it - No ROMS for UAE either)
kornfan71 said:
What is the best course of action to get back to Samsung Official/Normal status (USA or German), or can it even be done?
Thanks in advance for any help!
Click to expand...
Click to collapse
Personally I'd wait a few days. JB is rolling out now, and I don't really believe that the US (8013) version will be that long behind the others. So if you can wait, then just download the 8013 JB ROM when it arrives, flash it with Odin and you will be back to official. I would tend to ignore the Binary count for now (see question above) and then fix it when you get the 8013 JB and your ready to go "Official"

Thanks for the replies!
Bulbous said:
How are you checking that the Binary count is 2?
Click to expand...
Click to collapse
I'm just looking at the information at the top left of the screen when the device is in download mode.
Thanks for pointing me to ExynosAbuse. That will definitely make life easier when I go to reset the binary counter!
I'll probably just wait to flash an 8013 JB ROM once one is available. The 8010 firmware doesn't have 5GHz WiFi support, which I use frequently.
Thanks for the advice!

kornfan71 said:
Thanks for the replies!
I'm just looking at the information at the top left of the screen when the device is in download mode.
Thanks for pointing me to ExynosAbuse. That will definitely make life easier when I go to reset the binary counter!
I'll probably just wait to flash an 8013 JB ROM once one is available. The 8010 firmware doesn't have 5GHz WiFi support, which I use frequently.
Thanks for the advice!
Click to expand...
Click to collapse
That's funny. My 8013 on 8010 firmware works perfectly on 5 GHz wireless n.
Sent from my GT-N7100 using XDA Premium HD app

Same thing happened to me. My counter is up to 2 now, one for the German ICS and one for the German JB.
My hypothesis is that you can swap ROMS within the same model - so any 8010 ROM works fine on any 8010 without upping the count, but that going between models (8010 -> 8013) trips the counter.
However, as far as I can tell, everything works fine except the ability to update OTA and it might even be better since you're getting the version that's not been modified for the US market to get past the legal issues with Apple.
The only iffy part is that you're going to be stuck relying on XDA for updates.. but to be honest, the gang here has been pretty reliable in that area for years.

kornfan71 said:
Thanks for the replies!
I'm just looking at the information at the top left of the screen when the device is in download mode.
Thanks for pointing me to ExynosAbuse. That will definitely make life easier when I go to reset the binary counter!
I'll probably just wait to flash an 8013 JB ROM once one is available. The 8010 firmware doesn't have 5GHz WiFi support, which I use frequently.
Thanks for the advice!
Click to expand...
Click to collapse
I also installed the 8010 JB and now wi-fi direct between my GS3 and the Note doesn't work anymore.

I'm not rooted, will having the flash counter at 2, if I have an official rom flashed (and it says official in download mode), prevent me from getting an OTA?

tisoyboy2 said:
I also installed the 8010 JB and now wi-fi direct between my GS3 and the Note doesn't work anymore.
Click to expand...
Click to collapse
WiFi issue are VERY common when flashing roms from different regions. Every country has different frequencies & bands that can be used publicly & in the UK & Germany, they differ from here in the US. If you change your CSC files in system to identify as an en_US device, or more precisely, change the line in the wifi config file from ccode=gb to ccode=ALL , you will then get 5Ghz. I have no issues with AllShare or WiFi direct, but I changed the wifi config files & edited the csc files to show XAR region with all wifi channels open (ccode=ALL).
BTW, there was an 4.1.1 region XAR leak recently, a few days ago I think. I am also pretty sure someone, maybe Darkman, released a deodexed version of it. There are also dumps of it in the Dev section of the Note 10.1 forums.

[TUT] How to disable root checks for OTA updates (OTA with status = Modified)

Yes, apparently it's possible.
You will need:
-Galaxy S3 (tested on I9305)
-System status = Modified (obviously...)
-Secret Codes Revealer app (from Google Play)
1. Open the Secret Codes Revealer.
2. List Codes -> Launch custom code.
3. Enter 8736364 -> Launch code.
4. Menu -> Input MasterKey.
5. Enter "rooting" -> OK.
6. Rooting Off -> OK.
7. Go to your Phone Settings menu, and check for updates

We have similar threads already guiding users on how to unroot for stock OTA updates. Please check the stickies.

This is not about unrooting - this is about enabling OTA downloads on rooted phones (AKA overriding the root check).

Does it work ? like for real ?
Edit: My phone is no longer detected as a rooted phone

Darius_AWS said:
Does it work ? like for real ?
Edit: My phone is no longer detected as a rooted phone
Click to expand...
Click to collapse
But it's still rooted with all the privileges right ?

Still rooted (& root working), still showing Modified. Right now, I don't have any update available for my I9305, but it's definitely checking for updates.
I don't know if the FOTA engine will actually be able to apply a downloaded update to a rooted system partition - but it's a good way for obtaining OTA packages.
BTW, someone with a BTU I9300 please test - a slightly newer version of 4.3 is shipping via OTA (same PDA, new CSC, new modem compared to the Vodafone release)

Hmmm. You cannot start a tutorial with "apparently". It should be fully tested before its a tutorial.
Also, accepting ota updates on rooted devices is extremely bad practice so you should put a disclaimer in about that....
And also recommend only rooted stock (odexed) users do this
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

schetz said:
But it's still rooted with all the privileges right ?
Click to expand...
Click to collapse
Yes but the csc of my phone is Unknown so it's a bit pointless

I stand corrected on my previous reply before however having tried this... it doesn't work for me at all. Nothing happens after I inputted the code stated by the OP. And like rootSU said it's basically a bad practice on rooted phones users since you already know that rooting will limit if not make your phone make use of the ability to get OTA updates normally.

SignetSphere said:
I stand corrected on my previous reply before however having tried this... it doesn't work for me at all. Nothing happens after I inputted the code stated by the OP. And like rootSU said it's basically a bad practice on rooted phones users since you already know that rooting will limit if not make your phone make use of the ability to get OTA updates normally.
Click to expand...
Click to collapse
mate works for me on stock 4.3, although it states device status>custom, i am able to check for updates

I9305 lte mm1 region
this code not function to my s3.. i can't disable my root to do OTA update.. help..

SM-T320 March 2015 Firmware Upgrade

I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.

horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
IPTV or torrent tv, normally plays through mx player ?. Was a bug, half of the screen black
http://forum.xda-developers.com/app...f-screen-black-watching-t3017829#post58842303

That firmware is just for the UK, which I believe went to NI1 last fall about a month before the U.S. went to NK1.
I don't know that I'd read a lot into it. If anything, they could be getting UK firmware better aligned with other locations for a smoother universal upgrade to 5.
Edit: Okay, looks like it's indeed out now for the U.S., too. Still hoping it's progress towards a Lollipop upgrade.

So does anyone actually know what changes this update brought? I was having some issues with my tab pro 8.4 missing touches, i 1st noticed it during gaming but was able to replicate it with display tester multitouch test.
It seems to be fine now, i thought for sure it was a hardware defect but now I'm not so sure. Anyone else in a similar position as me?

Hey there
I m downloading it, but not sure i will apply it .. does it makes root going byebye ? Wanna stay with my device rooted !
thanks

I just downloaded and installed in California. Still 4.4.2 no issues so far.
Sent from my SM-T320

+1. Got excited over nothing.
johna2u said:
I just downloaded and installed in California. Still 4.4.2 no issues so far.
Sent from my SM-T320
Click to expand...
Click to collapse

Rooted device? Able to root after update?
Thx

Just finished updating and was very disappointed that it's still 4.4.2, I didnt check this forum beforehand so was hoping for a nice surprise.
I hope we see official 5.0 for our devices...

Still. Nothing here! Will we ever get lollipop?

biroot said:
Rooted device? Able to root after update?
Thx
Click to expand...
Click to collapse
Without thinking I took the update and lost root. So, I'm searching to see if root is available for the update.

Rooted T320UEU1AOC1
66gt350 said:
Without thinking I took the update and lost root. So, I'm searching to see if root is available for the update.
Click to expand...
Click to collapse
I rooted with Chainfire"s CF-Auto-Root for Odin. download.chainfire.eu/383/CF-Root/CF-Auto-Root/CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.zip (For T320). Main web page here autoroot.chainfire.eu/. As you know To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding! So don't forget http//:

Rooted i747 said:
I rooted with Chainfire"s CF-Auto-Root for Odin. download.chainfire.eu/383/CF-Root/CF-Auto-Root/CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.zip (For T320). Main web page here autoroot.chainfire.eu/. As you know To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding! So don't forget http//:
Click to expand...
Click to collapse
Thanks for the quick reply. Reading on the main page, did using the Chainfire's CF-Auto-Root trip the Knox Counter and the custom firmware counter?
thanks

A little bit less lag going from TW to Magazine tiles. Tried removing them with no luck. Hopefully this update sets us up for lollipop.
Sent from my HTC One mini using XDA Free mobile app

66gt350 said:
Thanks for the quick reply. Reading on the main page, did using the Chainfire's CF-Auto-Root trip the Knox Counter and the custom firmware counter?
thanks
Click to expand...
Click to collapse
It trips knoxs
Ported Note 4 on 3

Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again

M4r10 22 said:
Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again
Click to expand...
Click to collapse
I'm in the process of trying to line up everything to do this. My update that pushed through took me to T320UEU1AOC1. I haven't located the extracted US kernel file for that and unfortunately don't know how to pull it from my current build. Sammobile has an AOC1 file noted as Cellular South and the build time is same date as mine but different timestamp. Anyone know if that would work to get me back to my current build and keep my US region?

horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
How did you do this? I have mine rooted and have TWRP but can't figure out how to get that stupid Touchwiz back. Any help would be great
---------- Post added at 02:25 AM ---------- Previous post was at 01:27 AM ----------
horseycraze said:
I've just installed the latest firmware for the TabPro 8.4; KOT49H.T320XXUBOC1. Disappointingly, it's still 4.4.2 which makes me wonder if we'll ever see a L-pop upgrade. I've only been running it for a half-hour or so but can't notice any difference. I'll report back if there any major problems.
Click to expand...
Click to collapse
Could you put the steps I need in order to what you did here?

I have the Romanian version of the updated ROM on a T325.
The biggest issue I have noticed is with the light sensor, with the previous ROM the auto setting worked smoothly, now with the new ROM the screen doesn't fade continuously. Whenever I turn on the screen the brightness just switches from a higher to a lower setting or inversely (without smooth fading and with lag), also the screen flickers horribly when it detects a change so I can't use the auto anymore.
The second issue is with the Samsung keyboard with learning disabled, in a Facebook floating chat window I tried to respond to someone and the keyboard would auto complete with empty words and after every word I had to delete the word before to be able to write the next word. I had to re-enable the learning to get rid of this very annoying problem.
I will try to downgrade to the previous ROM and root it with towelroot and say goodbye to any future official Samsung updates. Samsung has the ****tiest update developers, actually I had the same problem with the auto light setting (but not so serious) with the ROM which was before the good one.
By the way, if Lollipop comes DON'T UPGRADE. Lollipop on S5 sucks bigtime, the phone has major issues, android eats more battery than the screen.
Stick with the previous ROM, for me it was the most flawless one. I might try a cache wipe on the current ROM but I doubt it has anything to do with the screen flickering.

M4r10 22 said:
Anyone try use towelroot method to root T320 without trip knox?
>flashing old kernel
>run towelroot
>flash new kernel again
Click to expand...
Click to collapse
stormygal said:
I'm in the process of trying to line up everything to do this. My update that pushed through took me to T320UEU1AOC1. I haven't located the extracted US kernel file for that and unfortunately don't know how to pull it from my current build. Sammobile has an AOC1 file noted as Cellular South and the build time is same date as mine but different timestamp. Anyone know if that would work to get me back to my current build and keep my US region?
Click to expand...
Click to collapse
After losing root when I took the T320UEU1AOC1 update, I was able to flash the T320 kernel in this thread then use Towelroot again. I did have to reboot, even though it told me I wouldn't need to. I uninstalled and reinstalled SuperSU (hit cancel when I got the SuperSU notice about Knox) and verified root with Root Checker Basic. Then installed the AOC1 kernel. I still have root and Knox is not tripped. (KNOX KERNEL LOCK: 0x0; KNOX WARRANTY VOID: 0x0)

[Early Warning] DO NOT TAKE OTAs after upgrading to Lollipop

If you've upgraded to the new Lollipop 5.0.1 update (N910VVRU1BOAF) for Verizon Samsung Galaxy Note 4 (N910V):
MAKE SURE YOU NEVER TAKE ANY OTA
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP​
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.

Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?

^^^I'm not sure, but I've been postponing mine since the Ota was pushed.

Hibby- said:
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
Click to expand...
Click to collapse
droidx2.3.3 said:
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.

When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"

itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
I believe your looking for "SDM"

rhilway said:
I believe your looking for "SDM"
Click to expand...
Click to collapse
You are correct.

Manually updating
hsbadr said:
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
Click to expand...
Click to collapse
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated

Nameless crowd face said:
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Click to expand...
Click to collapse
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!

So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?

hsbadr said:
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
Click to expand...
Click to collapse
Thank you again man

samhainww said:
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
Click to expand...
Click to collapse
I did last night, just use Odin to flash the NJ5 firmware, when it tries to boot the first time it will bootloop. Pull the battery, replace the battery and boot to recovery (vol up+home+power) then wipe data. The phone will boot to the setup wizard for KK.

I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk

starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.

starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Click to expand...
Click to collapse
Nameless crowd face said:
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+1
Another example, some Note 3 users fall into the trap of 4.4.4 OTA update & with no option to downgrade, they lost root, custom TW ROMs, and almost everything. Now, they're waiting with Note 4 users for a root method to rejoin the party while Note 3 on 4.4.2 can be rooted using TowelRoot.

Which tool?
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
All of the debloat tools that I find require root, which are you using?

There's a script that someone wrote to disable Ota and debloat. It doesn't need root. Sacher around on here for it

So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?

As of now it makes no difference.

Stupid question, but how do you turn off automatic OTA on lollipop?

Rooted but received ota update??

Hi guys i have g900f in the UK and i am on KK 4.4.2 Rooted with stock rom. Today i received a software update message, i went to software update and its showing me a update package of 194mb and its giving me the option to download it however i am rooted with towel root and knox 0x0.
Any ideas of this update? If i do it, would it wipe away my root? I have left a screen shot below. Thanks
Sent from my SM-G900F using xda premium

In all probability it will update the device to Lollipop. .....and that WILL remove your root access.
The only thing that is preventing me from being certain of the fact is the size of the download....194 Mb is very small considering a full LP firmware is somewhere in the region of 1.36 Gb.....
Do you have a reason for staying on KK or is it just that you haven't had an opportunity to upgrade to LP before today?
http://i.imgur.com/rVnFwJM.jpg

There is no Lollipop within Europe, until beginning of May.
Any phones it should have all latest security patches at any cost.

keithross39 said:
In all probability it will update the device to Lollipop. .....and that WILL remove your root access.
The only thing that is preventing me from being certain of the fact is the size of the download....194 Mb is very small considering a full LP firmware is somewhere in the region of 1.36 Gb.....
Do you have a reason for staying on KK or is it just that you haven't had an opportunity to upgrade to LP before today?
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
I like Kitkat as you can root it with Towel and have Knox 0x0. My warranty expires in August, so i am generally waiting for the official Marshmallow update, then i will upgrade the software to it.
Its werid how i got that update notification, because i restarted my phone earlier and checked again for updates, and it told me my device is modified and cannot update now. Maybe it was a glitch, but i am certainly not updating it to lollipop
Sent from my SM-G900F using xda premium

Yes if you have root access every one remotely has root access to your own phone too.
This is not a perfect world.

Kiriakos-GR said:
Yes if you have root access every one remotely has root access to your own phone too.
This is not a perfect world.
Click to expand...
Click to collapse
Could you please elaborate? I will be updating to marshmallow as soon as it drops with the latest security patches.
Sent from my SM-G900F using xda premium

While I am just a industrial electrician playing with motors , cables, and electronics, even so I am also aware of what is: Remote hijacking of a Smartphone.
Samsung security patches and lollipop (By Samsung) both are additional added shields against all sort of hijacking, due apps, remote access or direct unauthorized access.