I had My Knox on my phone prior to upgrading to Oreo for use with my work GSuite account. After upgrading, My Knox became Workspace. I have recently switched from Verizon to T-Mobile and after installing the T-Mobile firmware in order to unlock their bands, My Knox/Workspace was gone. Both apps appear to still be installed in the apps directory, but I can't figure out how to open it.
I know I can use Secure Folder since My Knox is officially discontinued, but (1) I prefer the launcher mode of Workspace and (2) setting it all up again is a hassle.
Any thoughts on how I can get Workspace back?
Sent from my SM-G930T using Tapatalk
Related
I was just wondering if anyone here has any experience with using Mobile Iron with a phone that has been rooted for a few small tweaks and then unrooted.. Does it work? Can Mobile Iron tell that you were once rooted but are no longer?
I've got an AT&T Galaxy S3 that was recently upgraded via OTG to Android 4.3 with Knox and the new bootloader, etc. Unfortunately, the 4.3 upgrade has disabled my ability to tether. I'd like to apply a mod that fixes that limitation, but I don't want to lose the ability to get work email and such on my phone via Mobile Iron.. Any thoughts on whether or not it should be possible to:
1. Temporarily uninstall Mobile Iron
2. Root my phone and apply the tether mod
3. Remove root from my phone
4. Reinstall Mobile Iron and have it work?
Any thoughts, suggestions, advice would be greatly appreciated!
Thanks
MrSimmonsSr
Sent from my Sero 7 Pro using Tapatalk 4
For the record, just wanted everyone to know this seems to have worked like I'd hoped! I used CF-Autoroot to root my S3 running 4.3.. (The first time I tried it I bricked my device because I didn't think to unencrypt it before I applied root. Don't do that! I had to flash the 4.3 update twice to get it all working again! )
But once I did that I was able to root the fresh install, remove tons of bloatware and apply a tether hack. Then I unrooted and reinstalled Mobile Iron and Touchdown.. So far no issues!
Sent from my Sero 7 Pro using Tapatalk 4
Hi Mr,
currently I am doing research on MDM solutions and I found some information about the detection methods MDMs use to detect root. The following four are commonly used (https://www.netspi.com/blog/entryid/209/android-root-detection-techniques):
1. Check default files and configs.
2. Check if there is a Superuser app.
3. Check permissions of some folders (i.e. /data)
4. Check is "su" commands can be executed.
I don't expect or expected it to cause any problems! Dependant on the security policy, installing some apps like thether hack, might cause a security alert though.
Sometimes applications that require root will trip the application that wants to ensure root doesn't exist. For example Citrix Home detected BusyBox existed on my system & thus flagged my phone as rooted.
There is also an Xposed Module which will attempt to hide root:
http://www.xda-developers.com/android/xposed-module-to-cloak-root-access-from-apps/
http://forum.xda-developers.com/showthread.php?t=2574647
It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.
i have s8+ g955u there's a problem in it Samsung Health, Secure Folder and Samsung pay is not working, i'm more curious about samsung health app it says "can't be opened on a rooted phone (0xffffc000#0030null61N2530)"
i have checked with different root checker apps, zint, terminal they all says the phone is not rooted,
root explorer does not open system file in which by changing an entry value from 0 to 1 we can use S health (it shows blank file tried with notepad++ and some other editors)
download mode value is 0x0
tried hard reset as well
now by reading some posts here i decided to install a stock rom but i am confused about which rom to install there are several roms available on sammobile, i'm using it in pakistan, (just bought this used mobile) and sammobile have shows different carriers of US, i want unlocked rom please help me to chose one
current build version: R16NW.G955USQU4CRE9
Cypherx.ninja said:
i have s8+ g955u there's a problem in it Samsung Health, Secure Folder and Samsung pay is not working, i'm more curious about samsung health app it says "can't be opened on a rooted phone (0xffffc000#0030null61N2530)"
i have checked with different root checker apps, zint, terminal they all says the phone is not rooted,
root explorer does not open system file in which by changing an entry value from 0 to 1 we can use S health (it shows blank file tried with notepad++ and some other editors)
download mode value is 0x0
tried hard reset as well
now by reading some posts here i decided to install a stock rom but i am confused about which rom to install there are several roms available on sammobile, i'm using it in pakistan, (just bought this used mobile) and sammobile have shows different carriers of US, i want unlocked rom please help me to chose one
current build version: R16NW.G955USQU4CRE9
Click to expand...
Click to collapse
After ROOT, brush back to the stock ROM and use the S health method.
1-Delete S-Health App
2-Install the old version 4 of the S-Health application
com.sec.android.app.shealth_4.8.1.0025-4810025.apk
3-Open the application and complete the setup
4-to the store to update the S-Health app
my english is bad ,i use google translation
Your knox has been tripped you may never use those function in normal circumstances, only thing you can do is s-health the person above me explains which version but secure folder is gone. Only solution is solder the e-fuse there where somewhere diagrams or change motherboard. There was an application or a method that claims to reset the knox to 0x0 even if the e-fuse is blown but i didn't see any real confirmation that it's real.
SOLUTION
the issue was, the firmware was not properly installed, i downloaded the official roms from sammobile then install it using odin, after that it's perfectly working even now it is automatically updated to android pie and everything is working fine, the bit is not trip
it happens when you don't add up all the required files in odin at the time of installation, so some official apps like secure folder and samsung health does not work.
thanks everyone for the help.
Rooted therefore lost Secure Folder.
Is there any way to get the Secure Folder working again whilst rooted? (I think some custom ROMs manage to do this...?)
Or is there a (preferably System level) reliable App lock alternative?
elmor0 said:
Rooted therefore lost Secure Folder.
Is there any way to get the Secure Folder working again whilst rooted? (I think some custom ROMs manage to do this...?)
Or is there a (preferably System level) reliable App lock alternative?
Click to expand...
Click to collapse
No. Secure Folder is tied to Knox. Rooting breaks Knox. Even if you go back to stock, it still won't work.
I understand about root breaking Knox.
But I've seen previous Samsung posts about getting Secure Folder to work with build prop editor mod/ Magisk fix module/ custom ROMs with working Secure Folder etc.
So just wondering if any expert or experienced person on this topic.....
as to having back knox, I think is not posible, but, I recall reading somewhere about hiding the rooted state to make some apps to work
Secure folder is working on both rooted VN and Dr. Ketan's rom. S22U 908E
I've hidden root successfully for relevant banking/ monitoring Apps, which otherwise wouldn't have worked if root not hidden.
Exactly my point, if custom ROMs can make Secure Folder work (Knox is still tripped), then is it possible to port this component over to rooted s22u - to have a working SF?
There is a TWRP group on Telegram for this device. Just look for afaneh92 Magisk modules. Secure folder is working fine on rooted Phone with this magisk module.
Afaneh92 Magisk Modules
You can view and join @afaneh92_magisk_modules right away.
t.me
Hi.
I unlocked the bootloader and rooted the phone with magisk. I can't install the island and shelter apps. The island application returns that the security policy prevents the creation of a work profile because a custom operating system is installed on this device. The case looks identical even when there is no root.
userned said:
Hi.
I unlocked the bootloader and rooted the phone with magisk. I can't install the island and shelter apps. The island application returns that the security policy prevents the creation of a work profile because a custom operating system is installed on this device. The case looks identical even when there is no root.
Click to expand...
Click to collapse
Congratulations! You have blown a fuse and Knox will NEVER work on your phone again.
I knew all about it. However, I am interested in a way to bypass this problem and restore at least application isolation.
Should i use multidisabler ?
Isn't it simpler to ask the islander/shelter app developer a question?
multidisabler nothing changed. In general, I can't manually create a profile using adb.