Related
Hey friends, I am very new to the rooting scene. I have a at&t htc m8 and i made the mistake of trying to root the fast and easy way. I followed a guide by a user names Unlocker. I would post the link but am unable to at this current time because i am new here
That has it's readers use hasoon2000's all in one toolkit. Well I think I screwed up in that process. when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. So naturally I freaked out tried my best to unroot the damn thing by following a guide created by the same guy after he got many complaints of issues
Naturally I had problems with this aswell. Now where i'm at, at this current moment is
**tampered** ***unlocked**
I successfully (i think) removed super su and did my best to get back to stock firmware. well I failed at that aswell. I still have TWRP on my phone and managed to get security turned back on.
What I am asking is for any references or maybe even some fresh help on how i can either get my phone back to stock firmware so i can take the OTA updates and be on my merry way or maybe reccomend a custom rom I can use that has the new lolipop software.
Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM. I feel pretty helpless right now but if i can get some instruction I know I will be able to figure this out.
I'm still really new to this also, but I'll try my best (just take everything I say w/ a grain of salt...):
Krob189 said:
... when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. ...
Click to expand...
Click to collapse
Do you mean that you'd successfully done whatever you were doing and this was happening in normal use? AFAIK it is normal for the the screen to power off during long-running TWRP actions, and power button wakes it up.
Krob189 said:
...
I successfully (i think) removed super su and did my best to get back to stock firmware. well I failed at that aswell. I still have TWRP on my phone and managed to get security turned back on.
Click to expand...
Click to collapse
Which firmware do you have on it now? Do you have ADB installed? If so, it might be helpful if you post the output of the command
Code:
fastboot getvar all
. If not, I think you'll need ADB and fastboot to help recover.
Krob189 said:
...Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM ...
Click to expand...
Click to collapse
AT&T uses GSM. The GSM version should be correct. Depending on the firmware you have installed, specific versions of twrp may not work. In my case, twrp 2.8.4.0 wouldn't work on AT&T's stock 4.4.2 firmware, but would on the 4.4.4 firmware.
EDIT: Did you make a TWRP backup before attempting these changes? Depending on the state of your firmware, restoring that might be enough to fix things.
AT&T Stock 4.4.4 RUU
This should solve your problem, if you can achieve s-off again:
AT&T Stock 4.4.4 RUU
Krob189 said:
That has it's readers use hasoon2000's all in one toolkit. Well I think I screwed up in that process. when my phone was off and charging , the screen would briefly flash the TWRP ui with their lock screen. So naturally I freaked out tried my best to unroot the damn thing by following a guide created by the same guy after he got many complaints of issues
Click to expand...
Click to collapse
All the panic is for nothing. Its normal for the TWRP screen to appear for a brief moment when the device is powered off, and you connect the charger. At least on older versions of TWPR (and the version installed by Hasoon's toolkit is quite old).
Krob189 said:
Now i was looking to update my TWRP but I am unable to locate an AT&T verison. I see sprint , verizon, and GSM. I feel pretty helpless right now but if i can get some instruction I know I will be able to figure this out.
Click to expand...
Click to collapse
The TWRP version you want is the GSM. All versions of the M8 are essentially the same (and considered "GSM") except for the CDMA (Sprint & Verizon) and dual SIM variants.
---------- Post added at 12:47 PM ---------- Previous post was at 12:46 PM ----------
brasticstack said:
Do you mean that you'd successfully done whatever you were doing and this was happening in normal use? AFAIK it is normal for the the screen to power off during long-running TWRP actions, and power button wakes it up.
Click to expand...
Click to collapse
What the OP is describing was a known bug, and happened when outside of recovery and while the phone was powered off (and while connecting the charger).
Wow thank you for fast responses!
So from my understanding I have a outdated TWRP version. I suppose I need to read up on how to update this and also how to flash a new rom. I only rooted my phone so I could pair up my ps3 controller to my phone so I can play games on it. I regret doing it now to be honest because I have modded my 3ds to play the same games i was using on my phone
I would love to be on the lolipop update that launched yesterday I believe. Should I stick to a rooted rom or just flash a stock version? Can anyone recommend a good lolipop root that has some tweaks for battery life and overall performance?
Krob189 said:
So from my understanding I have a outdated TWRP version. I suppose I need to read up on how to update this and also how to flash a new rom.
Click to expand...
Click to collapse
Just get the latest version of TWRP from their website. As you are asking what version (CDMA vs. GSM) it sounds like you are already getting there.
It sounds like you have the version of TWRP that was installed by the toolkit. That version is many months old. But its a minor bug, anyway. How often do you charge the phone with it powered off, anyway. I also don't think you can do anything in TWRP in this condition (if a security risk is your concern). The TWRP appears for a split second, and that's it.
Krob189 said:
I would love to be on the lolipop update that launched yesterday I believe. Should I stick to a rooted rom or just flash a stock version? Can anyone recommend a good lolipop root that has some tweaks for battery life and overall performance?
Click to expand...
Click to collapse
Lollipop didn't launch for AT&T, its just a long-delayed 4.4.4 update for us. To update to 4.4.4, either return to stock ROM and stock recovery to get the OTA, or relock the bootloader and run the official RUU.
Lollipop (5.0) started to roll out for some Euro CIDs, and has been out for US Dev Edition for a while. But you can't get to Sense Lollipop unless you s-off (or until AT&T releases it).
Hello,
As the title suggests, I'm looking for a way to completely backup my stock device without root.
This would include firmware and stock recoveries, basically system files - as I'm not really too terribly worried with saving personal data.
I've searched through various threads but I think I'm in one of those "in-over-my-head" situations, so let me explain why I haven't just flashed a custom recovery and made a nandroid backup.
My device is the C-Spire Note 5, SM-N920R7, running 5.1.1 - recognized by Smart Switch with no updates available.
I received this device in the mail today - because I somehow managed to brick my old device with the "custom binary blocked" FRP.
There is no stock firmware available for download to flash in Odin, and it was impossible to boot the device in regular or recovery mode, leaving me with Download mode.
In order to root my old device, I had to unlock the OEM in Developer Settings and flash the "Beastmode" kernel via Odin:
http://forum.xda-developers.com/spr...rnel-beastmode-modified-stock-1-0-sm-t3196174
Then, I flashed a TWRP recovery and used it to install SuperSU - and voila! I had rooted my device.
Fast forward a few months... My battery died one day and it somehow triggered the FRP lock - with only Download mode available and no C-Spire stock firmware to flash.
Naturally, I want to root my device again, but first I want to create a complete backup of my device that would be flashable in Odin even with the FRP lock on.
So ladies and gentlemen, any help or advice would be appreciated.
I would of course, upload my firmware publicly so that anyone else using this device doesn't brick their phone like I did.
Did you ever get an answer to this? I'm in the same boat and want to do the same thing.
theophile2 said:
Did you ever get an answer to this? I'm in the same boat and want to do the same thing.
Click to expand...
Click to collapse
The only way I've seen involves capturing temporary files during an update through Kies or Smart Switch.
Being on C-Spire, that probably will not ever happen.
Maybe C-Spire will get it together and push out 6.0.1 OTA like the rest of the world - as well as actually providing an alternate (non-OTA) download method.
Apparently some guy on the C-Spire Dev forums paid for a ROM on a Chinese site that works with our phones - which would serve as a nice backup if he would ever upload it.
I asked him to - and apparently he contacted the admins asking for a way to upload the file to the forums.
After they responded to him, he must have never uploaded the file.
i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root
Hey guys, so for a while I've had an S4 (I9505) and my YouTube subs/viewers want to see custom ROMS on it. So I used Kingoroot to try and get root access and it seemed to work (used terminal sim to check) and then I connected the phone to PC, put it in download mode and launched Odin to flash a new ROM (it was on 4.4 stock with no OTA update available to 5.0 for some reason?). Anyway long story short I got my settings so that it would delete all data before flashing. I go to flash and it fails early on due to the fact it can't write (or something along those lines). And I need help :c
Write protection is on and I have no ROM to boot into, nor a custom recovery. So I really need your guys' help :c
Please help me get it on some kind of working ROM :C
(rewards are awesome points and shoutout on 5.6k sub phone channel?)
TehMiik said:
Hey guys, so for a while I've had an S4 (I9505) and my YouTube subs/viewers want to see custom ROMS on it. So I used Kingoroot to try and get root access and it seemed to work (used terminal sim to check) and then I connected the phone to PC, put it in download mode and launched Odin to flash a new ROM (it was on 4.4 stock with no OTA update available to 5.0 for some reason?). Anyway long story short I got my settings so that it would delete all data before flashing. I go to flash and it fails early on due to the fact it can't write (or something along those lines). And I need help :c
Write protection is on and I have no ROM to boot into, nor a custom recovery. So I really need your guys' help :c
Please help me get it on some kind of working ROM :C
(rewards are awesome points and shoutout on 5.6k sub phone channel?)
Click to expand...
Click to collapse
I believe that is the google play edition... TWRP can be found here.
https://twrp.me/devices/samsunggalaxys4googleedition.html
Also stock firmware can be found here to flash with Odin to get you going.
https://www.sammobile.com/firmwares/galaxy-s4/GT-I9505/
Flash the stock firmware first and then flash the TWRP and make a backup.
Sent from my XT1609 using Tapatalk
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.