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:
Related
My phone is F&^%ed.
Its completely missing the efs folder. Its empty. (Yes its been rooted and files unhidden). There is nothing there.
I was to return it to warranty state and send it back to samsung.
How can I do this so the warranty isn't void?
Are there any particular files I need to remove? Won't there be logs and they can see what's been going on with the phone?
I've got copies if the stock rom and supposedly the stock kernal.
When I do *#1234# I get
PDA: 19100TDUFK4
PHONE: unknown
CSC: Unknown
Build info Weds June 29 17:28:38 KST 2011
Info phone info the kernal version is 2.6.35.7 19100ZSKF4-CL280225 [email protected]#22
I'm sure the Kernal used to say DELL.
Anyone know where to go next?
Get firmware for your country/carrier here, if you can't find it/if link is dead/if it isn't listed, do a search on here for Checkfus & you'll be able to download the latest firmware for your phone/carrier/country that you'd normally get via Kies.
Flash firmware in Odin, do a factory reset/make sure there are no apps left on the phone that could tip off whomever fixes it that you've been messing with it, jig it to reset the flash counter (if the jig doesn't work, flash the old bootloader from here in the PDA or Bootloader section of Odin, then the jig should work).
Getting warranty service after you've run non-stock firmware on the phone is never 100% certain after you've voided the warranty by doing same. But if you do the above, you will probably (not definitely) get warranty service.
If you're after 100% chance of warranty service, don't mess with your phone in the first place.
Done.
Return to your telco/Samsung.
Thanks!
The only reason I ever rooted the phone is because they refused to fix it under warranty due to a cracked screen.
After unlocking my phone with the code that 3 gave me, it stopped working. (No imei)
I send it back to be fixed and as there was a minor crack in the screen they wanted that fixed first.
So I did some research and realised what the problem was.
Apparently its common for a phone unlock to damage the efs.
And that's when I discovered rooting Never heard of it before. So it was not me mucking around with the phone that damaged the efs folder.
It took me a few weeks to realise that I'm never getting this fixed by myself so I've contacted the TIO about getting it fixed under warranty. From what I understand even Samsung cant repair a damaged efs. So they would probably just replace the phone.
I think its unfair that they want to charge me $250 for a screen that they have no intention of repairing, that I don't even want repaired, and is completely unrelated to the real problem.
I have a question. I've done a factory reset but 2 apps are still there. Superuser and clockwork, why weren't they deleted?
melodye said:
I have a question. I've done a factory reset but 2 apps are still there. Superuser and clockwork, why weren't they deleted?
Click to expand...
Click to collapse
Why would they be deleted if they are part of the firmware on the phone .
Follow the instructions flash stock rom to remove root .
jje
JJEgan said:
Why would they be deleted if they are part of the firmware on the phone .
Follow the instructions flash stock rom to remove root .
jje
Click to expand...
Click to collapse
LOL I don't know. I have done that. The firmware is original.
melodye said:
LOL I don't know. I have done that. The firmware is original.
Click to expand...
Click to collapse
Firmware cannot be original if you have rooted or installed root and cwm .
Factory reset = a restore of the firmware last flashed on the phone .
jje
JJEgan said:
Firmware cannot be original if you have rooted or installed root and cwm .
Factory reset = a restore of the firmware last flashed on the phone .
jje
Click to expand...
Click to collapse
Ok its stock. Its supposedly the stock rom that came with the phone. I didn't know that superuser came with the stock rom.
Hey all,
Had my S3 for about 10months.
HANDSET DETAILS:
* Unlocked GT-i9300 (running GiffGaff sim)
* 16GB White, running Stock Touch-Wizzed ICS 4.0.4
* Baseband: I9300BVLE4
* Kernel Ver: 3.0.15-554502-user
[email protected]#1
SMP PREEMPT Sun May 13 11:40:33 KST 2012
* Build Number: IMM76D.I9300BVALE4
WHAT I'M TRYING TO DO:
I am not trying to root this phone (YET!), I am just trying to use Kies to upgrade to JB.
All the 'legal information' in the Settings menu is 'greyed out'. I cannot select, or update OTA.
I will probably get to the CM / custom ROMs sometime but for now I just thought I'd do a simple (I thought) easy upgrade to JB.
Kies recognises the phone, suggests I do a back-up (which I did), and then attempts to download a 3000mb install package. At this point, it throws up a dialog box showing a bunch of 'square characters' - the kind of thing you see if you don't have a language installed on your OS. (which is XP by the way).
It's an error for sure, as after closing it (OK is the only option), the download process loops as it asks me again 'do I want to backup before upgrade'. So I'm getting nowhere.
I'm not sure why Kies has such a problem with my phone.
If it's any use, I can say that this was bought brand-new, unlocked, from a retailer website, though upon boot it displays an Orange logo, and certain parts of the menus (although very few) were in French by default. I've registered the phone with Samsung on their site successfully so that's fine. I put in a QUERY for them to help but it's been over a month and nothing back so far.
So I thought I would come to the expert village and see if I can get some help.
-I'm hoping it's okay to ask about Official updating here and not completely boring ( ! ) as I'm aware this is a land of great rootery and customisation! which I think is great by the way :good:
Thanks to anyone that can help!
regards,
SkEvol (newbie)
Have a look in the stickies about how to use ODIN (its not difficult to use).
Then, I would advise you flash the latest official Samsung firmware from here - http://forum.xda-developers.com/showthread.php?t=1646610
Ensure you follow the ODIN instructions properly and make sure Kies isn't running when you use ODIN.
This will get you onto the latest version of JB to be released by Samsung...
mikep99 said:
Have a look in the stickies about how to use ODIN (its not difficult to use).
Then, I would advise you flash the latest official Samsung firmware from here - http://forum.xda-developers.com/showthread.php?t=1646610
Ensure you follow the ODIN instructions properly and make sure Kies isn't running when you use ODIN.
This will get you onto the latest version of JB to be released by Samsung...
Click to expand...
Click to collapse
Hi there Mike,
Thanks for the reply, while I'm quite happy to use some ODIN to do this (I don't mind a learning curve), I'm just a bit put off by the disclaimer "Using ODIN can change your bootloader to show that the system is MODIFIED and may increase your ODIN flash count. This may void your Warrenty".
-my phone is still under warranty and I would rather avoid breaking the warranty if at all possible.
Are there any other options?
SkEvol said:
Hi there Mike,
Thanks for the reply, while I'm quite happy to use some ODIN to do this (I don't mind a learning curve), I'm just a bit put off by the disclaimer "Using ODIN can change your bootloader to show that the system is MODIFIED and may increase your ODIN flash count. This may void your Warrenty".
-my phone is still under warranty and I would rather avoid breaking the warranty if at all possible.
Are there any other options?
Click to expand...
Click to collapse
I wouldn't worry about that tbh.
As your phone hasn't been rooted it shouldn't be an issue.
Also, there are ways to change the system flag back to 'official' using Triangle Away but I don't think you'll need to.
Sent from my GT-I9300 using xda app-developers app
mikep99 said:
I wouldn't worry about that tbh.
As your phone hasn't been rooted it shouldn't be an issue.
Also, there are ways to change the system flag back to 'official' using Triangle Away but I don't think you'll need to.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks again Mike,
I'm going to use ODIN to update to Samsung's official I9300XXEMD2_I9300OXXEMD1_I9300XXEMC2_XEO.zip ROM.
I'm already using the Stock ICS which came with the phone (brand new, but unlocked). So essentially I'll just be updating to a new version of an official ROM from Samsung.
I have already taken steps using KIES, to backup the call logs, SMS's, contacts, and APPS.
These are all items which are stored on the internal 16GB (I believe) please correct me if I'm wrong?
I would like to ask:
1) Will this ODIN flashing process effect any data on my external SD card? (I obviously don't want to lose any of it)
2) And, will I be able to use KIES afterwards, to return all my old data (ie app settings, the APPS themselves, call logs, SMS's, contacts etc) to the phone's 16GB memory?
Hopefully simple questions :fingers-crossed:
Thanks again.
The ODIN process doesn't wipe your phone as far as I can remember so everything should still be there (downloaded apps, SMS, call log etc).
Hopefully someone else can clarify this who has used it recently...
Sent from my GT-I9300 using xda app-developers app
mikep99 said:
The ODIN process doesn't wipe your phone as far as I can remember so everything should still be there (downloaded apps, SMS, call log etc).
Hopefully someone else can clarify this who has used it recently...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for heading me in Odin's direction
I haven't gotten round to doing the update yet.. and considering just hanging on until samsung release their official 'non-leaked' JB s3 update.
I'm still in the dark as to why my update options / legal information are greyed out though..
Does anyone know why?
I'm still in the dark as to why my update options / legal information are greyed out though..
Does anyone know why?
usual reason is a mismatch in the phone codes shown to KIES .
Orange logo means its an Orange phone and based upon the OP i would suggest that its an Orange France phone originally . It may have had firmware modifications or been a return phone or even a grey import .That would explain wrong codes no update path .
jje
'Mismatch in phone codes shown to Kies'
Are you saying Kies is expecting a certain code from the phone?
(Presumably derived from its serial number or something) - I don't know what a 'phone code' is.
I never had a doubt this phone has been messed with.
Presumably then.. the warranty might have been void (technically) since the day I bought it.
Since the firmware has been messed with?
If you have a mismatch in the Phone and CSC Kies will tell you that you can't update when you connect it as its trying to update that wont be the problem.
Your baseband and build are defiantly Orange so you need to flash the latest Orange France version to keep warranty but would guess that if it doesn't have Orange bloatware on it then at some point its been rooted and the bloatware wiped, in which case you want have a warranty
The latest France Orange firmware is phone I9300XELLA csc I9300FTMELL1 from sammobile site but if you want non branded then you need Open Europe OXA or UK & Europe BTU, the one you mention XEO is Poland although it will work for you its not really the one you want but the choice is yours.
You don't need a rooted phone to use Odin but any update will increase your flash count you can zero this by using triangle away from XDA if you want.
EDIT :- Just noticed in your first post the version is from May 2012 that you currently have so is this phone previously used.
I own a Samsung Galaxy S6 Edge 32gb, SM-G925F, got it on a contract with Orange France. The phone isn't fake, it is a genuine Samsung unit, I purchased it from an official Orange shop in France, it is network locked as I am on a contract. I rooted it with Ping Pong method, rom was supported and root was successful, knox was not tripped. As I gained access to root, I went and deleted just some bloatware, absolutely nothing critical, and I need to stress on that, from /system/app and system/priv-app. I then rebooted only to see that the phone went into a bootloop. I then went into recovery, wiped cache, that didn't help. I then wiped user data/reset the phone from recovery, no joy after this either. Further more I noticed that in recovery, at the bottom, "dm-verity verification failed..." is written down in yellow. The only way I could revive the phone was by flashing the stock rom again via Odin 3.10. So basically, while ping pong root works just fine, something else prevents it from being useful, as the phone does not like anything at all removed from its system files. Hopefully, all of this makes some sense and I will get some helpful advice here. Apologies if me posting this here breaks any of the forum rules, but I did post the same issue on the ping pong root post and I had no replies basically and also there was no resolution that I could see presented on the other "dm verity verification failed..." posts. So, many thanks in advance indeed for any helpful advice some of you bright minds out there might have for this.
and you flashed correct firmware..?
carionix said:
I own a Samsung Galaxy S6 Edge 32gb, SM-G925F, got it on a contract with Orange France. The phone isn't fake, it is a genuine Samsung unit, I purchased it from an official Orange shop in France, it is network locked as I am on a contract. I rooted it with Ping Pong method, rom was supported and root was successful, knox was not tripped. As I gained access to root, I went and deleted just some bloatware, absolutely nothing critical, and I neestress on that, from /system/app and system/priv-app. I then rebooted only to see that the phone went into a bootloop. I then went into recovery, wiped cache, that didn't help. I then wiped user data/reset the phone from recovery, no joy after this either. Further more I noticed that in recovery, at the bottom, "dm-verity verification failed..." is written down in yellow. The only way I could revive the phone was by flashing the stock rom again via Odin 3.10. So basically, while ping pong root works just fine, something else prevents it from being useful, as the phone does not like anything at all removed from its system files. Hopefully, all of this makes some sense and I will get some helpful advice here. Apologies if me posting this here breaks any of the forum rules, but I did post the same issue on the ping pong root post and I had no replies basically and also there was no resolution that I could see presented on the other "dm verity verification failed..." posts. So, many thanks in advance indeed for any helpful advice some of you bright minds out there might have for this.
Click to expand...
Click to collapse
seems like some of the stuff you got rid of was critical to the os.
I has the same issue as yours. At first, I used the debloater tool and removed all apps listed here: http://forum.xda-developers.com/galaxy-s6/general/safe-to-debloat-s6-threads-t3090383. That caused the bootloops and dm-verity verification fail for me. I then noticed that when I used the tool, not all apps actually get removed even thought I instructed it to. So I used esf file explorer, mounted the system as r/w and then used its system app uninstaller to remove all the apps mentioned in the above thread. Its worked great for me. I think it has to do with some knox apps being left over when I used the first method.
tell me more about flashing stock rom...
hi so for short i have crashed my samsung s6 edge. firstly rooted it with kingroot it was all good. then modified build.prop and after reboot the phone is stuck in boot loop with the same "dm-verity verification failed". no help from factory restore so i suppose i would need to flash my stock rom? but i don't know how to get one.
thanks in advance
rank4 said:
hi so for short i have crashed my samsung s6 edge. firstly rooted it with kingroot it was all good. then modified build.prop and after reboot the phone is stuck in boot loop with the same "dm-verity verification failed". no help from factory restore so i suppose i would need to flash my stock rom? but i don't know how to get one.
thanks in advance
Click to expand...
Click to collapse
try: http://www.sammobile.com/firmwares/
sorry for double post
ok so i found out what is firmware and now i need to find out my SCS or PDA.
is there any way of finding this without working phone?
i know model: SM-G925F SAMSUNG, YATELEY, GU46 6GG. UK
IMEI:359521/06/392799/2 and S/N...?
how can i pick right firmware?
they don't seem to have the sm-g925a for att s6 edge. Does anyone have, or does a rev 3 or 4 version exist in the wild? been looking for 2 days. older versions will not flash, odin fails on AP and BL flashes.
http://click.xda-developers.com/api...amsung Galaxy S6 Edge | XDA Forums&txt=HERE.
found an android firmware for 5.1.1 att stock rom to repair corrupted imei issues.
I have a phone again, yay
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
Hello magix01
Hello magix01,
Could you kindly please help me?
I have SM-G920F and i have the same issue with it.
Skype ID: adryan_289
phone # : 0040724031461.
I'm scared because I can no longer use my phone. I have teamviwer,drivers, mic and everything that is needed.
Thank you.
magix01 said:
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
Click to expand...
Click to collapse
magix01 said:
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
Click to expand...
Click to collapse
Skype is nicolas.allaire
Number 1-450-712-9727
I am looking for help to bypass dm verity on my samsung galaxy s6 5.1.1 **920W8 (canada)
i have the same issue , plz help
skype id : doctor.ayan_isb
suhaibahmad said:
i have the same issue , plz help
skype id : doctor.ayan_isb
Click to expand...
Click to collapse
do you used what'sup?
anwr said:
do you used what'sup?
Click to expand...
Click to collapse
yes please send me message 00923452105231 or send me yours
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.
Hi! This is my first post here, so if I say something even relatively taboo, I apologize.
I recently picked up a Samsung Galaxy S4 from a seller on Letgo. However, it was formatted in such a way that it tripped the reactivation lock. The seller says they got it from a Goodwill listing, so he has no way of contacting the original owner. Even Samsung won't help, as they require a printed receipt.
At this point, I've rooted the phone via KingRoot and installed TWRP. (If anyone wants to find out how, hit me up!) With full su access and a terminal, is there a way to manually disable the reactivation lock and flash Lineage OS? If so, I'd be happy to know.
Thank you so much!
heyitzrare said:
Hi! This is my first post here, so if I say something even relatively taboo, I apologize.
I recently picked up a Samsung Galaxy S4 from a seller on Letgo. However, it was formatted in such a way that it tripped the reactivation lock. The seller says they got it from a Goodwill listing, so he has no way of contacting the original owner. Even Samsung won't help, as they require a printed receipt.
At this point, I've rooted the phone via KingRoot and installed TWRP. (If anyone wants to find out how, hit me up!) With full su access and a terminal, is there a way to manually disable the reactivation lock and flash Lineage OS? If so, I'd be happy to know.
Thank you so much!
Click to expand...
Click to collapse
What bootloader are you on? Given you have TWRP I am guessing it's MDK. Have you tried flashing the firmware you are on over what you have with odin? This will erase everything and bring you back to full 100% stock like it just came out of the box.
StoneyJSG said:
What bootloader are you on? Given you have TWRP I am guessing it's MDK. Have you tried flashing the firmware you are on over what you have with odin? This will erase everything and bring you back to full 100% stock like it just came out of the box.
Click to expand...
Click to collapse
Hey, thanks for the reply!
First off, how would I check this to make sure? I really don't want to permanently brick my phone.
Second, will this fix the bootloader flag?
Thanks!
heyitzrare said:
Hey, thanks for the reply!
First off, how would I check this to make sure? I really don't want to permanently brick my phone.
Second, will this fix the bootloader flag?
Thanks!
Click to expand...
Click to collapse
Goto settings, about phone, software info to find out what bootloader you're on. It'll be under "baseband". Look at the last 3 letters. If it says MDK you're in luck, do NOT update your phone or else you will patch the bootloader and thus will not allow TWRP anymore. What bootloader flag are you getting? Is TWRP working or does it give an "unauthorized software" message?
Samsung Galaxy s4 locked with original Samsung account... I factory data reset it and can't get access to that information... So can I bypass it?
You will need to find the pit file for it. I think I got mine from a zip file on androidfilehost called Samsung pit files or something similar. You will need the pit file for the jfltevzw. You will also need to download the firmware for it. In Odin click on the repartition tab and load up your pit file and then the firmware file under the AP section and let it run the reflashing process. This is what removed the reactivation lock for me. Turn off auto reboot and then reboot into Odin right away and it will say if the lock is still on or off.