Hi everyone,
Let me explain, I used odin to flash the recovery, because of the encryption or whatsoever I wasn't able to transfer via MTP using TWRP in order to get super Su on the phone to root and boot because of the dm-verity thing.
So I wipe data and then I could transfer super Su, get the phone rooted, and boot it up.
Of course Knox was tripped, so i can't access private folder nor S health, but I can live without it. (Ok, if someone know how to make S health work again I take it )
After all of that I tried to setup the Iris scanner again and it scan my eyes, says everything is okay, and goes back to the menu where it is written "add your iris".
No matter how many times I try it seems that it doesn't save my iris properly, or don't save it at all.
Do someone knows something about it ? for those that are rooted do you experience the same issue ?
Thanks in advance
PS : I rooted following this tutorial : http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3458413
Hello.
I did root my sm-n9300 following the tutorial.
Only SHealth didn't work.
To put it working again is easy:
Go to playstore, and downgrade the SHealth. Never allow to upgrade it again.
About the iris scanner, I had my iris saved before rooting, and didn't have to scanner it again.
The private folder works fine.
You didn't follow exactly the tutorial.
After flashing the recovery, you can tranfer su via MTP, using the sdcard, and then flash it.
Maybe if you flash the official firmware via Kies, and do the process of rooting again, you will have the iris and private folder working.
Hoppe this will help.
Hi, thanks for the answer!
In fact I wasn't able to transfer SU via mtp, for some reason twrp wasn't able to mount anything, so I had to format data, in order to "break" the encryption.
Maybe I'll try to flash the firmware with Kies and do it all over again.
But I don't get how secure folder can be working for you if knox is tripped...
Hello.
Indeed you are right.
The private folder don't work.
i thought it did, because everytime I was seeing photos, I got an information to put them in that folder, if I wished
But never did. Now I tried, and got a message saying the Knox couldn't create it.
My mistake
Sorry. But the iris do work, indeed
I really don't have any clue about how to fix the iris scanner
Trying to use a secure feature where one side of security has been compromised, i.e the ability of any app to have root privileges. I think there is a reason for the Iris scanner to not be working... Admittedly I used to enable root I every phone as I do normally tinker at system level, but, more and more apps are doing what normally root was needed for these days, the need to root is really low now. With my corporate policy basically blocking any knox tripped device, I have kind of learnt to get by without root and luckily that is now paying off with some convenience features that you can only really use in a secure environ safely like Android pay, fingerprint and iris unlock etc. Now my phone is effectively a wallet, I really want those secure features maintained so something more sinister is somewhat blocked from making its way into there.
Sent from my SM-N930F using Tapatalk
I see your point, the fact is when trying to set up the iris scanner there is no message about compromised security like when trying to open the secure folder.
In fact it works, it just seems to not be able to save it properly.
My phone is also a wallet in China since wechat pay and alipay can be use even on rooted phone, and it also can be use everywhere. ( no need of special terminal or whatever special technology, just a bar code scanner)
Thanks for your answer, I think k I'll try a factory reset tomorrow and let you know
I remember when setting up either finger print scanner or iris, the phone brought up a message about knox environment being activated, so I think you will be out of luck.
Be careful with rooted phone in China, I connected my rooted phone to my Chinese wife's laptop, and it installed an app with root privileges unattended!! I was not impressed with that I can tell you.
Sent from my SM-N930F using Tapatalk
it is bcoz u have disabled encryption in twrp .... if u want to use iris dnt clear encryption in twrp ....
sun2sunny said:
it is bcoz u have disabled encryption in twrp .... if u want to use iris dnt clear encryption in twrp ....
Click to expand...
Click to collapse
OK!
But how can I enable the encryption then?
I can't mount anything in twrp tough....
That is what I m searching next a days
Sent from my SM-N9300 using XDA Free mobile app
sun2sunny said:
That is what I m searching next a days
Click to expand...
Click to collapse
I guess the only way is to use a custom kernel, it will disabled knox and s health last version and iris scanner will work again
SylverSun said:
I guess the only way is to use a custom kernel, it will disabled knox and s health last version and iris scanner will work again
Click to expand...
Click to collapse
Where can we find it another question
sun2sunny said:
Where can we find it another question
Click to expand...
Click to collapse
Yes, maybe on some Chinese forum
Searched already
Related
Bypass(Reset) Lock screen Pattern/Password/PIN/Fingerprint scanning without wipe
We know it's a big pain when you forget PIN/Passowrd/Pattern and you simply can't afford to wipe device as you don't have backup.
Then What?
You were all the night busy with your new beast and when you wake up in morning and notice that your GF/BF took revenge by registering and locking device by his/her fingerprint
Then what?
Very simple. Flash attached file from recovery.
dr.ketan said:
Bypass(Reset) Lock screen Pattern/Password/PIN/Fingerprint scanning without wipe
We know it's a big pain when you forget PIN/Passowrd/Pattern and you simply can't afford to wipe device as you don't have backup.
Then What?
You were all the night busy with your new beast and when you wake up in morning and notice that your GF/BF took revenge by registering and locking device by his/her fingerprint
Then what?
Very simple. Flash attached file from recovery.
Click to expand...
Click to collapse
Thx. But this not work for me ....
I lost my saved finger scanner sample after a nandroid restor.... and after i flash this zip i always got a google keep fc
I have tested and it reset unlock options to swipe. Still finger print registration remain there. But device will be unlocked
Sent from my SM-N910G using xda premium
Great Stuff...Hats off Dr. Ketan
Need to figure out bypassing roam restrictions in download booster
My company policy makes me enter a 6 digit password. It's just a pain. Can I bypass this restriction? They have made their app as device admin.
does this work on more devices like galaxy s5?
Wait, does this mean that the passkey and fingerprints are not secure since everyone can use this to reset/bypass the lock without wipe?
Obviously. Once your device is rooted / CWM installed, there is always chance to modify your system.
elroy944 said:
does this work on more devices like galaxy s5?
Click to expand...
Click to collapse
Usually samsung device have common storing location for PW PIN etc. SO I believe it should work on S5 too. You can try it, I don't believe it will affect anything else even it fail to reset.
Just like that...?
I take it this needs a custom recovery?
So... all a thief has to do is flash a custom recovery from download mode and then flash this file to get past fingerprint scanner and even a strong alphanumeric password?
DONT KNOW WHETHER TO LAUGH OR CRY!!
ceo.mtcl said:
My company policy makes me enter a 6 digit password. It's just a pain. Can I bypass this restriction? They have made their app as device admin.
Click to expand...
Click to collapse
try the app Nine, its an exchange email app which lets you set the 6 digit on the app as opposed to the phone, so you can unlock the phone as per normal with swipe but when you want to open the email app (Nine) then only do you put your 6 digit code, works like a charm, just an idea cos as far as I know there is no exchange security bypass as yet.
Jostian said:
try the app Nine, its an exchange email app which lets you set the 6 digit on the app as opposed to the phone, so you can unlock the phone as per normal with swipe but when you want to open the email app (Nine) then only do you put your 6 digit code, works like a charm, just an idea cos as far as I know there is no exchange security bypass as yet.
Click to expand...
Click to collapse
I logged in only to thank you on this suggestion. This is one awesome app and my device is finally mine again
I set up pin code on the app + full encryption of the data, so it's very safe, all the draconian admin policies from my organizations admins are now gone, plus my device is now intelligently set to have automatically enable pin when I'm not at home.
If anything I have now double security because when I'm not at home, the device requires PIN and the corporate mail does too + it's all encrypted. Well worth the money.
What about for reactivation lock. Is it secure?And can i flash that zip file with stock recovery. My phone is not rooted.
This does not work on Galaxy S5
Did you use Odin to flash this file? Is so can I get some feedback on how because odin doesnt take .zip files. Since I do not have access to the file system, I can't move the files on to phone. Is there another way to flash this files to the galaxy 4 note. I am from the world of iPhone Jailbreaking and helping out a friend.
stat1124 said:
Did you use Odin to flash this file? Is so can I get some feedback on how because odin doesnt take .zip files. Since I do not have access to the file system, I can't move the files on to phone. Is there another way to flash this files to the galaxy 4 note. I am from the world of iPhone Jailbreaking and helping out a friend.
Click to expand...
Click to collapse
With Odin you flash your custom recovery. Flash attached file from recovery, it's said in OP.
Have fun
I took a nandroid backup with fingerprints registered, when ever i restore, it does not recognise my finger prints and even the backup password says incorrect. I tried flashing the utility but no luck. Any work around for the solution as i had to factory reset from recovery to clear the data
It's known issue. Before making nandroid remove registered finger prints.
Sent from my SM-N910G using xda premium
Can this be used to erase the stored fingerprints and reset them?
i used a nandroid backup and while i'm not locked out of the phone, i am locked out of changing fingerpring settings - and the backup password is corrupt as well.
Having a constant "Security Notice" on phone since rooting. Everything else works fine. Is there anyway I can maybe deactivate this function?
freeze in titanium backup...
Y0sHii said:
Having a constant "Security Notice" on phone since rooting. Everything else works fine. Is there anyway I can maybe deactivate this function?
Click to expand...
Click to collapse
to get rid of the security notice you will get(because the system is now rooted) simply install root explorer(or any root browser) and go to /system/app and delete securitylogagent or go into the folder and rename it adding .bkp to the end of the file name and reboot.
per
http://forum.xda-developers.com/showpost.php?p=68675715&postcount=2
I began getting this, too, after rooting my Note7. I solved it the way others suggested, with Titanium Backup by freezing the Security Log Agent. That worked for me.
SkyPhone said:
I began getting this, too, after rooting my Note7. I solved it the way others suggested, with Titanium Backup by freezing the Security Log Agent. That worked for me.
Click to expand...
Click to collapse
do you still have knox? i use samsung pay and security folder
You used the sprint method root at the N930V PHE or PH1? Not really related to thread, but just out of curiosity.
Same problem....
I'm having this same problem with my rooted note 7.
I've searched everywhere for securityagent on my note 7 and it's not there. The only way I can remove this threat found/restart device, is to remove device maintenance.
But then I lose the app done function and the advanced setting power saving mode.
I have disabled all knox and security realated apps.
But still still get the threat while device maintenance is there.
Does anyone know what the equivalent to securitylogagent is on a note 7 ????
Any help would be much appreciated, I am a noob, until 3 days ago I knew nothing, but I managed to unlock frp and root my note 7, but its been stressfull. I need help now...thanks.
Kellya86 said:
I'm having this same problem with my rooted note 7.
I've searched everywhere for securityagent on my note 7 and it's not there. The only way I can remove this threat found/restart device, is to remove device maintenance.
But then I lose the app done function and the advanced setting power saving mode.
I have disabled all knox and security realated apps.
But still still get the threat while device maintenance is there.
Does anyone know what the equivalent to securitylogagent is on a note 7 ????
Any help would be much appreciated, I am a noob, until 3 days ago I knew nothing, but I managed to unlock frp and root my note 7, but its been stressfull. I need help now...thanks.
Click to expand...
Click to collapse
You should have a package named SecurityLogAgent. Disabling this will stop the security notifications due to rooting. If you're referring to the Samsung messages regarding the recall, then you need to disable the Samsung Push service or just the notifications.
8
I'm not referring to them notifications, I have disabled Samsung push.
There is no package with the name 'securitylogagent' on my note 7.
I have researched this alot before joining and posting here. Its simply not there, no matter what I use to look for it. Just not there..
I would really like device maintenance back.. that's how iv got it disabled at the moment.
I am referring to the 'that found/restart device" warning that flags up in device maintenance.
Kellya86 said:
I'm not referring to them notifications, I have disabled Samsung push.
There is no package with the name 'securitylogagent' on my note 7.
I have researched this alot before joining and posting here. Its simply not there, no matter what I use to look for it. Just not there..
I would really like device maintenance back.. that's how iv got it disabled at the moment.
I am referring to the 'that found/restart device" warning that flags up in device maintenance.
Click to expand...
Click to collapse
Strange, there should be a folder at system/app/SecurityLogAgent
What firmware version are you on? What have you used to look for it?
I'm on 6.0.1, that I rooted on Sunday after I accidentally updated package disabler. I am a complete noob and have managed to just about get to this point without help.
I have looked for it using titanium backup, root browser and device control. It doesn't show on any...
So I have disabled a load of other things including device maintenance, com.samsung.andoid.sm.devicesecurity, and security manager service...
I was hoping one of these was the equivalent of securitylogagent.
Does this information below help?
Kellya86 said:
I'm on 6.0.1, that I rooted on Sunday after I accidentally updated package disabler. I am a complete noob and have managed to just about get to this point without help.
I have looked for it using titanium backup, root browser and device control. It doesn't show on any...
So I have disabled a load of other things including device maintenance, com.samsung.andoid.sm.devicesecurity, and security manager service...
I was hoping one of these was the equivalent of securitylogagent.
Does this information below help?
Click to expand...
Click to collapse
So by the build number I see that you are not on a Verizon firmware so the app names may be different. It appears you have UK firmware so you will have to find what the app name is for that firmware.
What I can suggest is that the next time you get the notification, long press on the icon at the left. You should be taken to the notification options for that app and you should also see an app info button on the right. you may be able to track the actual app down using this info or at least disable notifications.
Thanks for your reply.
Oh crap, I'll never find it then...
Is there a way I could post an image of my system so as some experienced members on here may look at it.??
Thanks again.
Hi all,
Joining Team Pixel tomorrow after my debacle with the Huawei Mate 20 Pro and the green screen fiasco.
Just wondering if its still worth rooting the Pixel? If i do it i wanna do it straight away to save wiping my data again when unlocking the BL. My main reasons would be for Adaway, Removing the Nav Bar, Swift theme installer and Viper.
Most of these can be done via ADB now so is it still worth rooting?
Rooting this phone is pretty easy and it doesn't impact the updating process much if you know what you're doing, so I vote that it is definitely worth rooting.
I don't use a lot of root apps, but the two main ones are worth it to me. I use AdAway for ads (VPN ad blockers are slower and have several cons) and an app called Sa2ration to compensate for the screen's weak color.
I have everything working the way I want without any compromises. Very happy with my setup.
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
I've always had an Android phone that has been able to be rooted. Adaway, V4A, Substratum, Sa2ration, Titanium Backup and removing the stock navigation buttons are the biggest things for me currently with the Pixel 3 XL.
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
So, in my opinion, unlocking the bootloader is a no brainer on these phones, right from the get-go.
With that said, rooting is much more user preference. I found no reason to root my OnePlus 6. However, with the 3 XL my sole reason for rooting is to edit the build.prop to properly hide the nav bar at the system level, allowing me to use gesture controls without issue. You can use ADB commands to achieve this as well. But my experience in trying to hide the nav bar with ADB commands on this phone has caused some wonky things to happen, such as status bar notifications not going away and volume controls getting cut off when watching something in landscape mode. Rooting the phone and editing the build.prop was the only solution that worked for me to hide the nav bar without running into unforeseen issues.
If you are one to do other things like use Magisk modules and such, then rooting will be a no brainer for you. Also, as someone else mentioned, rooting this phone is the most straight forward/simple experience I've had rooting a phone in years.
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
Try this: [Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + by Homeboy76 do #4 then #8 if you want root. Also, Prerequisites has a link to download SDK Platform tools r28.0.1, if it needs updating.
gettinwicked said:
It's soooo easy to root, I'm not sure why anyone wouldn't. My main reason is viper 4 android, but adaway, pixel launcher mods (changes icons and has a system UI tuner), and sd maid pro having deeper access for cleanup as well.
Click to expand...
Click to collapse
I'm perfectly happy with the stock experience on this phone. I have no need for anything that requires root. I've rooted a lot of phones in the past, but there's something about this one that I just feel no need to do so. To me that says a lot for how far Google has come.
I'm getting my pixel 3 xl in a few hours today and I've been up all night watching pixel 3 xl videos. I was just about to post a question like this, but thanks to you I don't have to! The wonders of searching.
Anyways, I agree for adway and maybe even mods.
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
I also want to do it out the box.
Also don't know about the new gesture stuff, so if I don't like it, I'd probably want to mod it.
Guitarfreak26 said:
Thanks guys thats it decided then. Is it best to OTA to november then root via twrp after ul bootloader.
Yeah nav bar is a pet hate of mine, I used to love LMT launcher, might try the OP gestures though on this one
Click to expand...
Click to collapse
That is exactly what I did with both a Pixel 3 and a Pixel 3 XL. Just don't do a permanent install of TWRP on the XL unless you want to lose your touch screen in TWRP with no way out of TWRP when it boots back in there. I ended up having to hold the power button down until I forced the device off. Booted back into bootloader and ran the temp TWRP (which strangely works fine for touch) and then ran Magisk again to get back to the OS. Strange, the regukar Pixel 3 took permanent TWRP after Magisk, rebooted to TWRP was still able to use touch commands and ran Magisk again to get back to the proper boot image. I can even go to TWRP normally, and touch is functioning normally. I'll have to write the stock boot image when I get home today so I can get back to stock recovery until TWRP for XL is fixed.
GunToYoMouth123 said:
What bothers me is if I decide to use Google pay, Pokemon go or using my bank app, because I was told rooting can stop them from allowing me to use them.
Click to expand...
Click to collapse
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
I've been learning to live with stock ROMS, BUT, I still need my root. Adaway, TiBu, Substratum, LMT Launcher. I can't give 'em up.
Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
Ohh okay, thanks for that input !
My pixel 3 XL just got here !
Going to see what's up !
Sevael said:
Magisk has a hide feature built-in that has been working for me. I have several apps that normally detect root and Magisk blocks their detection 100%. My banking app works (normally detects root) and Google Pay is working just fine with Magisk hide.
Click to expand...
Click to collapse
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
J32A said:
My banking apps work fine but i can't get google pay to work. Even with magisk hide still not work. "This account already exists on your device" wheni try to sign in
Click to expand...
Click to collapse
Not sure, I haven't encountered this.
I find that when an app has detected root, sometimes they retain this information even through reboots. In those situations, clearing all data from the app often fixes it.
Something else to be aware of is that if you have a widget for an app that detects root, it's not uncommon for the widget to load before Magisk finishes loading and hiding after a reboot. On my Pixel 2 I had one app where after each reboot it would load first (due to a widget being present) and would detect root and block itself. I had to remove the widget and just just use a normal shortcut to the app instead, as I would never manually open it before Magisk finished loading up fully.
I just got pixel 2 xl this thing is a beast came with 5g and unlimted data when I got tablets for kids literally no download it's all instant. every phone I have had b4 is rooted most still work. My question will I improve anything by rooting with this speed? I don't think a VPN blckr would slow it down. How hard is it to reverse root if I need warranty? Is this speed the 5g or just Google built a great product?
sn0warmy said:
I always recommend unlocking the bootloader right out of the box, even if you never plan to root. The sole reason for this is if at any point something goes awry and you end up in a bootloop or somehow end up soft bricked, with an unlocked bootloader you can be back up and running like new with a very quick flash-all script from the latest factory image on Google's support site. However, with a locked bootloader, if you find yourself in one of those bad situations, you're at the mercy of Google support to either get you a new device or go days without a phone while they try and fix it.
<snip>
Click to expand...
Click to collapse
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
bobby janow said:
Unlocking the bl is problematic in some instances. Detection for apps and things like that. Why would you just not check off the "allow the bootloader to be unlocked" option in OEM unlocking? Then you get to fastboot and can unlock if needed without actually being unlocked and compromised.
Click to expand...
Click to collapse
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Sent from my Pixel 3 XL
Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
No I don't think so. If you bl unlock it will be detected. There are kernels that will fix that but stock unlocked is a trigger.
Eudeferrer said:
It is my understanding, and correct me if I'm wrong, that apps recognize root but not bootloader locked status. As long as you don't root, you should be fine with all apps.
Click to expand...
Click to collapse
Yes. As @bobby janow said, some apps treat bootloader unlock as having root. DirecTV Now is a prime example. Also, Netflix won't even appear in the app store and would have to be sideloaded. Although, all of those can be worked around it is sometimes a pain.
Hello,
Need some help. I was able to get TWRP on my new Tab S4 and root it with Magisk without issue. I was trying to install and get Island working so I could sandbox a few apps for privacy and I can't get it to work. A Knox notice keeps coming up "The work profile cannot be created because the OS was changed". Then I give Island root access, it appears to work, then a lovely Knox screen (The Knox work profile Icon) comes up saying an unauthorized application was installed and blocked, please contact your admin. So I spent the next 4 hours combing forums and Island's install doco to find a solution. I have tried everything, I used debloat to turn all the Knox stuff off but the needed work space. I even left work space running but just disabled the Knox models in it. I installed Island manually with ADB, and gave it God rights. That made things worse.... Now this nasty screen came up at boot and forced me to recover the OS because it couldn't be bypassed, if just prompted to factory reset the device. I have exhausted all my known options and am now requesting air support.
Thanks in advance,
One Very Frustrated Android Amature
DevinN said:
Hello,
Need some help. I was able to get TWRP on my new Tab S4 and root it with Magisk without issue. I was trying to install and get Island working so I could sandbox a few apps for privacy and I can't get it to work. A Knox notice keeps coming up "The work profile cannot be created because the OS was changed". Then I give Island root access, it appears to work, then a lovely Knox screen (The Knox work profile Icon) comes up saying an unauthorized application was installed and blocked, please contact your admin. So I spent the next 4 hours combing forums and Island's install doco to find a solution. I have tried everything, I used debloat to turn all the Knox stuff off but the needed work space. I even left work space running but just disabled the Knox models in it. I installed Island manually with ADB, and gave it God rights. That made things worse.... Now this nasty screen came up at boot and forced me to recover the OS because it couldn't be bypassed, if just prompted to factory reset the device. I have exhausted all my known options and am now requesting air support.
Thanks in advance,
One Very Frustrated Android Amature
Click to expand...
Click to collapse
Afaik once knox 0x1 is triggered there is no way to use Island since work profile cant be added. In fact i tried a lot of stuff to get it working on stock software with just recovery and root being installed, tried unrooting going back to original stock.. nothing worked.
OS has been changed probably refers to the knox counter.
Unfortunately Samsung locks Knox if you unlock your device. Afaik this is irreversible.
That is the reason I am still on stock.
Edit: Island should still work though. Haven't tried it though.
spookyspookster said:
Unfortunately Samsung locks Knox if you unlock your device. Afaik this is irreversible.
That is the reason I am still on stock.
Edit: Island should still work though. Haven't tried it though.
Click to expand...
Click to collapse
Is that an OS limitation? I have other rooted Samsung tablets, (older) running like 5.1 and 6.1 and they WORK. Island is able to create its OWN sandbox with root access on those. I feel like this is a security applet / process blocking this only, not a technical limitation. I was able to create the work profile with ADB outside of root access, I was able to assign Island with both Device Owner and Admin over the work profile and it was technically working. Some Knox security process that I didn't disable (most likely because it's a com.system that isn't listed in debloat) that is blocking it from displaying (I believe it is working) with a security overlay that I can't close. I need help finding that, and killing it with fire. I think it is beyond me technically. I am a network admin, not programer, though I speak some programming basic concepts via my network background. Just enough to get me in trouble and get to to here to ask for help.
dr460nf1r3 said:
Afaik once knox 0x1 is triggered there is no way to use Island since work profile cant be added. In fact i tried a lot of stuff to get it working on stock software with just recovery and root being installed, tried unrooting going back to original stock.. nothing worked.
OS has been changed probably refers to the knox counter.
Click to expand...
Click to collapse
Ok, after much OCD digging, I found the permissions and the Knox security file that was popping that up. I deleted the permissions with adb, killed those 2 processes within the workgroup files using root deleter app and now it works. Note, the whole drive is decrypted by default, I applied the decrypt patch when I rooted. So island was able to successfully provision a work profile and is admin over it.
DevinN said:
Ok, after much OCD digging, I found the permissions and the Knox security file that was popping that up. I deleted the permissions with adb, killed those 2 processes within the workgroup files using root deleter app and now it works. Note, the whole drive is decrypted by default, I applied the decrypt patch when I rooted. So island was able to successfully provision a work profile and is admin over it.
Click to expand...
Click to collapse
Hi,
Would you be able to provide a step by step guide ?
Thanks
DevinN said:
Ok, after much OCD digging, I found the permissions and the Knox security file that was popping that up. I deleted the permissions with adb, killed those 2 processes within the workgroup files using root deleter app and now it works. Note, the whole drive is decrypted by default, I applied the decrypt patch when I rooted. So island was able to successfully provision a work profile and is admin over it.
Click to expand...
Click to collapse
A guide please?!:good:
DevinN said:
Ok, after much OCD digging, I found the permissions and the Knox security file that was popping that up. I deleted the permissions with adb, killed those 2 processes within the workgroup files using root deleter app and now it works. Note, the whole drive is decrypted by default, I applied the decrypt patch when I rooted. So island was able to successfully provision a work profile and is admin over it.
Click to expand...
Click to collapse
Please provide your method, i think we are a lot in that situation : rooted and no work profile allowed by knox and tima. I even tried custom kernels announcing knox stuff disable and it's not workin either.
Thks.
Nvm
DevinN said:
Ok, after much OCD digging, I found the permissions and the Knox security file that was popping that up. I deleted the permissions with adb, killed those 2 processes within the workgroup files using root deleter app and now it works. Note, the whole drive is decrypted by default, I applied the decrypt patch when I rooted. So island was able to successfully provision a work profile and is admin over it.
Click to expand...
Click to collapse
Hi how you do this I need to do the same. Thanks
Seriously, he shared the news but didn't share how he did it??
Please provide details
Anybody has a solution on this topic or is this thread dead?
@DevinN, can you provide more info please? What files and apps did you delete?
Edit:
I found that package "com.samsung.android.knox.containeragent" causes the black block-screen, so i disabled it. (adb shell pm disable ...).
Island still refuses fo be installed automatically (security policy prevents creation of work profile because a custom os has been installed) or using root (cannot start the work profile user)
Code:
TZ_init: : TZ_init Process: Device tampered, tamper fuse is set!
TZ_init: : trustlet initialization failed
trogper said:
@hardkeyboard, can you provide more info please? What files and apps did you delete?
Edit:
I found that package "com.samsung.android.knox.containeragent" causes the black block-screen, so i disabled it. (adb shell pm disable ...).
Island still refuses fo be installed automatically (security policy prevents creation of work profile because a custom os has been installed) or using root (cannot start the work profile user)
Click to expand...
Click to collapse
I replied to DevinN, I wish I know when I write post, but now I don't need because use Nicelock with multistar with dr. Ketan rom with secure folder working
I suppose there is no update here or any idea what permissions and knox security file we are talking here ?
I have this tablet which is being restricted to use due to Knox. It appears to be for some vendor. It takes over the device even though it's not connected to the internet and doesn't allow me to do anything with it. I have read all the threads I can find and tried every possible option through Odin to install new firmware.
I understand this model is a giant pain due to Verizon and I may not be able to root this for customization. But is there not a way to get a factory clean firmware on here that doesn't have this Knox vendor customization? If not, is this good for anything or just throw it in the trash?
popguru said:
I have this tablet which is being restricted to use due to Knox. It appears to be for some vendor. It takes over the device even though it's not connected to the internet and doesn't allow me to do anything with it. I have read all the threads I can find and tried every possible option through Odin to install new firmware.
I understand this model is a giant pain due to Verizon and I may not be able to root this for customization. But is there not a way to get a factory clean firmware on here that doesn't have this Knox vendor customization? If not, is this good for anything or just throw it in the trash?
Click to expand...
Click to collapse
Same issue but I added another user and it works fine because knox isn't running device admin. Owner doesn't work and either does usb debugging. I'm thinking of calling know for remote support.
I beat frp on this same tablet before
popguru said:
I have this tablet which is being restricted to use due to Knox. It appears to be for some vendor. It takes over the device even though it's not connected to the internet and doesn't allow me to do anything with it. I have read all the threads I can find and tried every possible option through Odin to install new firmware.
I understand this model is a giant pain due to Verizon and I may not be able to root this for customization. But is there not a way to get a factory clean firmware on here that doesn't have this Knox vendor customization? If not, is this good for anything or just throw it in the trash?
Click to expand...
Click to collapse
Can u create a geust user account ? If so activate this accou t log into that account download the apk and run the very popular one click root app that i wont say but kinda rhymes with bingo shoot any ways run the apk (it wont root your device) and instal it the run the root app itll get to 99% and then quit but the entire device will be like outta the box new as far as the os goes you wont have frp lock or anything
Sorry for the run on sentence and idk how old this thread is but anyway and shout ouf to whoesever red car is with lisence plate xda guy in canada just not the country
Grimlinkush said:
Can u create a geust user account ? If so activate this accou t log into that account download the apk and run the very popular one click root app that i wont say but kinda rhymes with bingo shoot any ways run the apk (it wont root your device) and instal it the run the root app itll get to 99% and then quit but the entire device will be like outta the box new as far as the os goes you wont have frp lock or anything
Sorry for the run on sentence and idk how old this thread is but anyway and shout ouf to whoesever red car is with lisence plate xda guy in canada just not the country
Click to expand...
Click to collapse
Thank you for the response. This is still very much an active question for me.
I'm able to create the user account, install and start the install for the mentioned apk. However, it stops at 90%, and I get this error "Root Failed" Error Code 0x166508. It recommends I use the PC version, but USB Debugging is disabled in main account and I can't even access Developer tools for this new account.
Additionally, I'm unable to use the Home button. I get the following message "Security policy prevents use of Home key"
Seems like no matter what is suggested, there is something new that is blocking this from being used.