Hi friends,
I successfully rooted (LineageOS) and then "unrooted" my Samsung S9+ by flashing it with the official firmware and switching off "OEM unlock" in settings.
Well, Google Pay, banking apps, Microsoft Teams - all them consider this device as "healthy", but Samsung Pass do not. I guess first reflash destroyed in some ways Knox, right? If this is a case - are there ways to restore this state as well?
Thank you!
doka.ua said:
Hi friends,
I successfully rooted (LineageOS) and then "unrooted" my Samsung S9+ by flashing it with the official firmware and switching off "OEM unlock" in settings.
Well, Google Pay, banking apps, Microsoft Teams - all them consider this device as "healthy", but Samsung Pass do not. I guess first reflash destroyed in some ways Knox, right? If this is a case - are there ways to restore this state as well?
Thank you!
Click to expand...
Click to collapse
well, thats the thing about knox. you cannot. only a samsung authorized service can restore that. so either get it to a samsung service or buy a new one. either way, you will have to pay.
Related
Hello everyone!
i have samsung galaxy s3 (i9300).
and i have updated it with last LOS build "lineage-14.1-20170621-nightly-i9300-signed.zip", but nfc pay still doesn't work.
Android Pay says "nfc is needed in stores. This device does not support NFC payments, so you won't be able to use Android Pay in stores."
Does anyone have SGS3 and could anyone check this?
P.S.: I have original samsung nfs battery. And in the another apps nfc worked correct. I can write and read information by nfc in underground card.
It is very possible that android pay won't work because your device is rooted. I cannot test this because my device is rooted too and I don't use android pay.
There is a logical reason for my thinking. With root you have access to things you shouldn't and it is easy to compromise the android pay app should you have root access. This can only be tested by trying the app on a stock device that has never seen root or has been unrooted properly to show no evidence.
To do that, you must have a non-knox device. If knox is triggered you cannot reset it as that is a permanent change. Triggering knox shouldn't interfere but I imagine the security of android pay may look for this too. Knox is for businesses to know if the device has been tampered with. It is not for making the device any more data secure than a device without knox. It is purely a 'byte flag'.
AFAIK, the device must show 0 custom flashes, "original" custom binary and "official" status. This can be achieved via triangle away and flashing the stock rom, eventually ending up at a completely "out of the box" state device. Then android pay 'should' work as intended.
Beamed in by telepathy.
shivadow said:
It is very possible that android pay won't work because your device is rooted. I cannot test this because my device is rooted too and I don't use android pay.
There is a logical reason for my thinking. With root you have access to things you shouldn't and it is easy to compromise the android pay app should you have root access. This can only be tested by trying the app on a stock device that has never seen root or has been unrooted properly to show no evidence.
To do that, you must have a non-knox device. If knox is triggered you cannot reset it as that is a permanent change. Triggering knox shouldn't interfere but I imagine the security of android pay may look for this too. Knox is for businesses to know if the device has been tampered with. It is not for making the device any more data secure than a device without knox. It is purely a 'byte flag'.
AFAIK, the device must show 0 custom flashes, "original" custom binary and "official" status. This can be achieved via triangle away and flashing the stock rom, eventually ending up at a completely "out of the box" state device. Then android pay 'should' work as intended.
Beamed in by telepathy.
Click to expand...
Click to collapse
This issue is not exactly in "root" device, because "root"-device show another message, and also i have no root.
I read about this problem deeper - Samsung Galaxy S3 from CM11 to CM14.1 not support Host card Emulation (HCE).
I am trying to understanding, is it possible HCE enable in SGS3 and why it was not done?!
PS: There is issue CYAN-2935 about this problem on the old jira...
After doing some research it appears that most devices that accept hce have an official kitkat firmware. Some s3's didn't get a kitkat update at all. I doubt hce can be activated on a device that doesn't support that feature so you need to confirm which device you have. Only the s3's that have 1.5gb RAM got the kitkat update but that doesn't necessarily mean it is capable, it's just a step in the right direction. Have you checked to see if there's an app which could tell you if your device is capable?.
If you have only 1gb RAM then forget hce on that device.
Beamed in by telepathy.
And some verions of galaxy s3 with 1.5gb ram - has no nfc )
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Have not heard before that people have gotten Knox tripped by flashing Samsung firmware, you could have by mistake flashed TWRP or an non Samsung partition file etc. But atleast try a factory reset. If that does not work, you tripped Knox:/
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
notsotet said:
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
Click to expand...
Click to collapse
It's official stable release of Android Pie with region code DBT. It mess things up when I had a device with NEE as a region?
I don't know maybe I just live with this and wait for the official Nordic Android Pie update.
Tuikelo said:
It's official stable release of Android Pie with region code DBT. It mess things up when I had a device with NEE as a region?
I don't know maybe I just live with this and wait for the official Nordic Android Pie update.
Click to expand...
Click to collapse
Being that I'm in the US I can't say for sure what the issue is because I haven't gotten the official stable build yet.
I'd say just flash back to stock official 8 for your region and wait for the ota. Shouldn't be too much longer for you.
Tuikelo said:
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Click to expand...
Click to collapse
I would double check to make sure you didn't trip knox... The following steps should help do this
Completely power off off your Galaxy S9+
Restart the phone in Download Mode
Once in download mode, visually search for the words "Warranty Void" and the numbers that are on the same line.
If the numbers show “0x0” knox has not been tripped.
If the numbers show “0x1” knox has been permanently (as in you can't fix it ever on that phone because an E-Fuse has been blown) tripped
Assuming that knox is still intact then I would believe the issue (I would say 80% if I had to guesstimate) due to the mismatch between the rom file you flashed and the existing bootloader, partition, csc, etc. that you didnt flash. For example if parts of the rom are from oreo and the android OS is the pie beta this could cause problems. I am not sure if they did this or not, but it would make sense that Samsung incorporated some sort of file/firmware/version integrity check
An easy way to tell if this is the case is to get all the firmware versions to come from the same release. In effect Can you restore it back to the way it was before you flashed the device? Or if possible can you update it fully so that all the files are the same firmware? Which ever route you go will be up to you, but overall if the files all come from the same firmware version if the apps in question work this will confirm the cause.
Also double check the firmware your flashing... If it is a release before the official beta's you may run into problems. Your gonna have to go ask in the board/forum you got the file from (in the respective thread) for help or check up on known issues. Otherwise if the use of Samsung pass and secure folders is of importance to you I would revert back to the firmware you were on (before you attempted to flash the beta) and wait for the official release.
The use of mismatched firmware parts can also cause you to not get any OTA updates, so your gonna have probably flash it again properly to correct that
Lastly if I recall correctly if you have enabled OEM unlock this can cause samsung pass and secure folders to not work.
notsotet said:
It's a beta for Android P right? It may say that due to you having a flashed the beta. Google pay tells me the same thing and until the official ota comes out, if you wanna use Samsung Pass just flash back to Oreo
Click to expand...
Click to collapse
The Google Pay thing is because Google Play Protect Certification Status has flagged the device as not certified. This is because we are currently using an unreleased (i.e. beta test from Samsung) firmware version. Once we are on an official release the Certification Status will revert to certified status and Google Pay will work.
The issue with Google Pay under the Android Pie beta does/should not effect Samsung Pass or Secure Folder at all. Currently on my install of the beta test version(s) Samsung Pass, Samsung Pay, Samsung Health and Secure Folder (all which rely on knox) work just fine. I am using them all the time without issue, with the exception of a few cosmetic aspects at first that have been resolved by Samsung.
he can also type "getprop" in adb shell or a terminal app and look for the warranty..
but as someone else already suggested, if you flashed a "beta" pie build that could absolutely cause it to read as custom (this wouldnt trip knox though) which would cause some issues with those apps..
if it is unnoficial/reading as custom, you should be able to check in settings > about phone > status then look for "Device Status".. I think its there in Pie..
to put into perspective, i simply disabled some apks.. im on a usa note 9 which means i couldnt root, unlock or trip knox if i wanted to but simply disabling some apps causedmine to show custom as u can see in my screenshot lol
Tuikelo said:
Hey there fellows!
Recently I flashed stable Android Pie German rom with Odin to my Samsung Galaxy S9+ Nordic countries (NEE). Everything went fine and device seemed to be official state under device information and Knox status told me I didn't trip Samsung Knox.
After setting my phone up I tried to open Samsung Pass and I got notificated that my device has been rooted and I will not be allowed to use Samsung Pass anymore and same goes to Safe Folder.
Does anyone know did I really trip Knox or is this just because I only flashed Android to device and not any else rom files (bootloader, partition, csc etc)?
Click to expand...
Click to collapse
I flashed the stable Pie update (DBT) as well and I'm not receiving that notification/error when I open Samsung pass. Flash all of the files in the zip (use HOME_CSC if you want to keep your data) and see if that helps.
Solution
I did a reload of oreo on my s9+ after doing an update to android 9 (Australian versions ) which I didn't like. My
google and Samsung pay would not work until I switched back off "OEM unlock" in "Developer tools" which erases your phone again like it did when you turned it on to load firmware with odin. The option is locked out and takes a week of being turned on to come back up.
Hello. I am new to the Forum. I recently purchased a Samsung Galaxy S9+ and would like to know what is the best stable root our there? What options are out there to save up battery life, delete unwanted applications and so on. I am a Apple user and I am here to learn about Android, rooting and other types of tips and tricks.
Thank you.
Just read and read this forum because rooting and custom rom specific to your device type. Just remember:
1. Custom recovery (TWRP) then backup EFS immediately. Copy somewhere either PC or cloud, this is your imei. Without imei, no call and sms. Then you can flash whatever custom rom that match your device.
2. Do not flash anything that're not for your device specifically. Always check and recheck G965f or G9650 or G960.
3. Upgrade or downgrade version should be on official. 8.0 to 8.1 should flash official 8.0 -> official 8.1 -> custom 8.1. Some may result blank imei. If you've backup EFS, relax, just flash last rom you remember with your imei intact then restore EFS.
These are the basic rules. Backup EFS, device type check, version match.
Why do you think you need to root? I mean, coming from iPhone, the S9+ is going to do so much more than the Apple. There's very little need to root in 2019.
Make sure you do your research fully, rooting trips Knox and will result in some apps not working (you can hide the root from the apps do they work, but knox is a physical switch so cannot revert once done).
I would recommend reading up on SABS as this allows you to block ads and disable unwanted apps/ services without rooting.
sarjarim said:
Just read and read this forum because rooting and custom rom specific to your device type. Just remember:
1. Custom recovery (TWRP) then backup EFS immediately. Copy somewhere either PC or cloud, this is your imei. Without imei, no call and sms. Then you can flash whatever custom rom that match your device.
2. Do not flash anything that're not for your device specifically. Always check and recheck G965f or G9650 or G960.
3. Upgrade or downgrade version should be on official. 8.0 to 8.1 should flash official 8.0 -> official 8.1 -> custom 8.1. Some may result blank imei. If you've backup EFS, relax, just flash last rom you remember with your imei intact then restore EFS.
These are the basic rules. Backup EFS, device type check, version match.
Click to expand...
Click to collapse
Ok, Thank you!
HellDiverUK said:
Why do you think you need to root? I mean, coming from iPhone, the S9+ is going to do so much more than the Apple. There's very little need to root in 2019.
Click to expand...
Click to collapse
I want to experience its full performance. I have played with it and honestly the camera is bad, battery drains so much faster than the iPhone, the ram always goes low and so on. I want to get rid of all the bloatware, save battery so it lasts for at least a day and just enjoy the phone.
ThatMANGUS said:
I am a Apple user and I am here to learn about Android, rooting and other types of tips and tricks.
Click to expand...
Click to collapse
You should of done some research before purchasing the phone, your tmobile s9+ isn't rootable.
HellDiverUK said:
Why do you think you need to root? I mean, coming from iPhone, the S9+ is going to do so much more than the Apple. There's very little need to root in 2019.
Click to expand...
Click to collapse
Exactly, i haven't rooted my phone since the nexus 5 and i really don't miss it. There are ways of blocking ad's with knox and disabling apps/services with regular apps.
ThatMANGUS said:
I want to experience its full performance. I have played with it and honestly the camera is bad, battery drains so much faster than the iPhone, the ram always goes low and so on. I want to get rid of all the bloatware, save battery so it lasts for at least a day and just enjoy the phone.
Click to expand...
Click to collapse
To disable bloatware, you don't have to root, install package disable from playstore.
peachpuff said:
You should of done some research before purchasing the phone, your tmobile s9+ isn't rootable.
Exactly, i haven't rooted my phone since the nexus 5 and i really don't miss it. There are ways of blocking ad's with knox and disabling apps/services with regular apps.
Click to expand...
Click to collapse
My s9+ is international unlocked. When i put a different sim cards in it, it changes the boot image etc.
To enjoy Android you should have brought the OnePlus phone.... You choose the wrong phone...?
ThatMANGUS said:
My s9+ is international unlocked. When i put a different sim cards in it, it changes the boot image etc.
Click to expand...
Click to collapse
Never saw that on any Samsung phone... and I had S3/S7/S9... they never switched boot image because of switching SIMs...
Sent from S.G. S9+ Duos
sentinelvdx said:
Never saw that on any Samsung phone... and I had S3/S7/S9... they never switched boot image because of switching SIMs...
Sent from S.G. S9+ Duos
Click to expand...
Click to collapse
If i put a AT&T Sim card in, the AT&T boot will start. If I put in a T-Mobile sim card in, the T-Mobile boot will start and so on.
Hi.
I bought recently an S9+ and I noticed that SAMSUNG apps like ( SAMSUNG pass, SAMSUNG pay, SAMSUNG Health, and Secure folder) does not work . The phone is not rooted and Knox is not tripped x0x.
I try to wipe data and update the android version to 9.0 but the problem is not solved.
Can anyone help me please :crying: .
SM-G965F/DS
AP: G965FXXU5CSF2
CP: G965FXXU5CSF2
CSC: G965FOXM5CSF2
Angel_of_darkness said:
Hi.
I bought recently an S9+ and I noticed that SAMSUNG apps like ( SAMSUNG pass, SAMSUNG pay, SAMSUNG Health, and Secure folder) does not work . The phone is not rooted and Knox is not tripped x0x.
I try to wipe data and update the android version to 9.0 but the problem is not solved.
Can anyone help me please :crying: .
SM-G965F/DS
AP: G965FXXU5CSF2
CP: G965FXXU5CSF2
CSC: G965FOXM5CSF2
Click to expand...
Click to collapse
Is OEM unlock toggled on? If so turn it off to relock the bootloader.
If that's not the case then usually when those things are not working only thing I know of that would most likely be due to root being present on the phone. Even if it was unrooted there maybe traces left of it on the phone.
In any event you could try flashing the full firmware via the patched odin.. You would need the firmware from a place like sammobile.com or samfirm app
Perhaps someone else with the same model might have some other ides and will chip in some advice
scottusa2008 said:
Is OEM unlock toggled on? If so turn it off to relock the bootloader.
If that's not the case then usually when those things are not working only thing I know of that would most likely be due to root being present on the phone. Even if it was unrooted there maybe traces left of it on the phone.
In any event you could try flashing the full firmware via the patched odin.. You would need the firmware from a place like sammobile.com or samfirm app
Perhaps someone else with the same model might have some other ides and will chip in some advice
Click to expand...
Click to collapse
The OEM unlock is off and the phone is not rooted because of Knox is not tripped.
I received the phone with android 8.0, SAMSUNG apps does not work, so I try to wipe data and update it from sammobile to android 9.0 unfortunately the problem is not solved :crying:
Angel_of_darkness said:
The OEM unlock is off and the phone is not rooted because of Knox is not tripped.
I received the phone with android 8.0, SAMSUNG apps does not work, so I try to wipe data and update it from sammobile to android 9.0 unfortunately the problem is not solved :crying:
Click to expand...
Click to collapse
Not sure what else to suggest... Barring any sort of regional restriction that would prohibit the use of those apps (not sure if one exists or not) for you... If you did the proper and correct firmware flash via odin then it should work.
There is a reason why those apps are not working, and all of them depend on knox. The only thing I know of that would cause all of them to not work would be if the device had been rooted before.
Are you able to return the phone and get a replacement?
scottusa2008 said:
Not sure what else to suggest... Barring any sort of regional restriction that would prohibit the use of those apps (not sure if one exists or not) for you... If you did the proper and correct firmware flash via odin then it should work.
There is a reason why those apps are not working, and all of them depend on knox. The only thing I know of that would cause all of them to not work would be if the device had been rooted before.
Are you able to return the phone and get a replatcement?
Click to expand...
Click to collapse
First of all thank you for reply,
I also think about regional restrictions so it makes sense, Knox is not tripped so the phone couldn't be rooted , and I do the update properly from sammobile .
Unfortunately I can't ask for replacement,
If I find the solution I'll post it.
Thank you :good:
I've successfully rooted my Galaxy Note 3 to play custom boot animations and boot audio. But now I want to try it on my main device; the Galaxy Note 20 Ultra. I only want to modify "bootsamsung.qmg", "bootsamsungloop.qmg", and try adding "PowerOn.ogg". (Is this even possible on newer Samsung phones?)
Thing is, I don't want to root this device because I still want to get security patches and updates without doing complicated flashing procedures, and I still want to get OEM support.
Is there a way to at least root the phone temporarily without voiding the software legitimacy, and still get support for updates?
(If not then guess I'll just wait till 2025 when the phone stops getting software updates)
ASEM1123 said:
I've successfully rooted my Galaxy Note 3 to play custom boot animations and boot audio. But now I want to try it on my main device; the Galaxy Note 20 Ultra. I only want to modify "bootsamsung.qmg", "bootsamsungloop.qmg", and try adding "PowerOn.ogg". (Is this even possible on newer Samsung phones?)
Thing is, I don't want to root this device because I still want to get security patches and updates without doing complicated flashing procedures, and I still want to get OEM support.
Is there a way to at least root the phone temporarily without voiding the software legitimacy, and still get support for updates?
(If not then guess I'll just wait till 2025 when the phone stops getting software updates)
Click to expand...
Click to collapse
It's a "have one's cake and eat it too" problem.
yes, you can modify phone without rooting phone.
no, you can't modify phone without losing knox/warranty.
no, you can't receive updates on modified phone.
aIecxs said:
yes, you can modify phone without rooting phone.
no, you can't modify phone without losing knox/warranty.
no, you can't receive updates on modified phone.
Click to expand...
Click to collapse
Ah, so even if it's not rooted it'll void the legitimacy when modified?
well that's a bummer
ASEM1123 said:
Ah, so even if it's not rooted it'll void the legitimacy when modified?
well that's a bummer
Click to expand...
Click to collapse
It is obvious that root is a modification of the system.
on locked bootloader no modifications allowed by secure boot chain of trust.
you already trip knox when unlocking bootloader, even if running completely stock ROM.
yeah, i was just hoping if there was a way somehow.
Thanks y'all.