Related
Hi all, apologies for an other thread.
There are so many threads on XDA/ reddit that are sort of related to this, but I can't seem to get the help I need or keep up with them all, so once again apologies, but I have really tried to find the answers myself before asking.
Basically, I did a factory reset/ wipe on my phone, did a clean install of 6.0.1 from the factory images. Side loaded 7 from the OTA update and nougat is great!
I installed the latest TWRP (after a few go's, managed to get it to stick), then installed the latest, N supported SU.
SU is installed and I can run as rooted. However, this is the part I don't understand (very new to all this). While I apparently have root, I can't get an app to move applications over to the system directory like I used to be able to do, doing the same setup.
So, is this something to do with system/ systemless root, or encryption or N, or have I stuffed something?
From all the reading I come up with encryption, then others said it doesn't matter if encrypted... So maybe it's just N and root doesn't support moving to the system...
Anyway, I'm totally lost now. Bottom line is, I can use apps that require root, but no apps that move applications to system can access system, even after granting root access to them.
Cheers.
reeza said:
Hi all, apologies for an other thread.
There are so many threads on XDA/ reddit that are sort of related to this, but I can't seem to get the help I need or keep up with them all, so once again apologies, but I have really tried to find the answers myself before asking.
Basically, I did a factory reset/ wipe on my phone, did a clean install of 6.0.1 from the factory images. Side loaded 7 from the OTA update and nougat is great!
I installed the latest TWRP (after a few go's, managed to get it to stick), then installed the latest, N supported SU.
SU is installed and I can run as rooted. However, this is the part I don't understand (very new to all this). While I apparently have root, I can't get an app to move applications over to the system directory like I used to be able to do, doing the same setup.
So, is this something to do with system/ systemless root, or encryption or N, or have I stuffed something?
From all the reading I come up with encryption, then others said it doesn't matter if encrypted... So maybe it's just N and root doesn't support moving to the system...
Anyway, I'm totally lost now. Bottom line is, I can use apps that require root, but no apps that move applications to system can access system, even after granting root access to them.
Cheers.
Click to expand...
Click to collapse
Something is messed up. TWRP shouldn't take a few tries to stick. The factory images are out now. Flash them and start over.
Sent from my Nexus 5X using Tapatalk
I factory wiped my phone under Marshmallow, and then updated it to Nougat with the OTA update, but when I boot up, I discovered that I am only proposed to add fingerprints to the phone. I am not offered to add a password for encryption. In the settings menu, adding a password does not appear anywhere. And it says the phone is already encrypted.
I don't understand what is going on. How can I encrypt the phone using a password?
fnoingw said:
I factory wiped my phone under Marshmallow, and then updated it to Nougat with the OTA update, but when I boot up, I discovered that I am only proposed to add fingerprints to the phone. I am not offered to add a password for encryption. In the settings menu, adding a password does not appear anywhere. And it says the phone is already encrypted.
I don't understand what is going on. How can I encrypt the phone using a password?
Click to expand...
Click to collapse
You don't see an option above fingerprint under security in settings (swipe)? Click it.
With kudos to @Captain_Throwback and company, I was able to install the latest OTA (January security update) for the M9 despite being rooted (systemless, phh/Magisk) and having TWRP 3.0.3-0 installed - just tapped 'install' when prompted and off we went (yes, I'll have to re-install TWRP, but still, wow).
My phone is encrypted and during the update I noticed that I was not prompted to decrypt it. Instead, I saw the message "Device decrypted with default password" come up. This is new to me, and a little disconcerting - but perhaps this is normal for this kind of update process? I'm unfamiliar with Linux in general and the command-line side of Android in particular, but if someone could tell me a bit about this, I'd appreciate it - is this normal behavior? And if so, how is it not a security risk (ie, a backdoor around my password/encryption)?
Thanks,
Computerslayer
That just means you don't have a password set up "on boot" in Android, which means it's encrypted with the default password, which is simply "default_password". So TWRP applies that and is able to decrypt your device automatically. If you want to be prompted to enter a password in TWRP, add a password "on boot" in Android.
Captain_Throwback said:
That just means you don't have a password set up "on boot" in Android, which means it's encrypted with the default password, which is simply "default_password". So TWRP applies that and is able to decrypt your device automatically. If you want to be prompted to enter a password in TWRP, add a password "on boot" in Android.
Click to expand...
Click to collapse
Ah! That makes sense. It seems I disabled this when I enabled Lockdown Pro as an accessibility service. I've got the password back in place for boot now. Thank you.
Thank you also for the latest version of TWRP and the ability to install OTAs with TWRP installed. With the advent of monthly security updates, it's nice to be able to have TWRP support installing them easily.
computerslayer said:
Ah! That makes sense. It seems I disabled this when I enabled Lockdown Pro as an accessibility service. I've got the password back in place for boot now. Thank you.
Thank you also for the latest version of TWRP and the ability to install OTAs with TWRP installed. With the advent of monthly security updates, it's nice to be able to have TWRP support installing them easily.
Click to expand...
Click to collapse
No problem - just make sure you manually install that firmware!
Captain_Throwback said:
No problem - just make sure you manually install that firmware!
Click to expand...
Click to collapse
Yeah, I've gotta still do that.... (pardon me while go re-read your instructions again)
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 the phone updated to android pie and rooted with magisk the latest version and i have twrp recovery on it
but while installing one of the mods (youtube vanced) and after it rebooted the phone asked for my pattern (not on the lock screen but the encrypted startup feature which i didn't turn on but i have changed my pattern a few days ago but i use the fingerprint always on the phone)
i forgot the pattern for the phone and i tried on it and it says 9 more tries and my phone will be wiped
is there a way to find the pattern on my google account since it's linked to the phone and it automatically uploads it to the cloud ? or is there a way to bypass it ?
Note:i know it sound like i stole the phone but i have proof of ownership if anyone wants(the box and the google account linked to it are mine and is linked to this account)
thanks in advance
Do you have access on twrp? If entered first time pattern should be saved and you can access data.
Simply reboot in twrp, if no pattern is asked make a backup of data partition (that will be unencrypted) just in case you will need to wipe and search for a way to access twrp-saved pattern.
You could also try the google feature "find my device" and change pattern, but as phone its encrypted i dont really think it will work.
mac12m99 said:
Do you have access on twrp? If entered first time pattern should be saved and you can access data.
Simply reboot in twrp, if no pattern is asked make a backup of data partition (that will be unencrypted) just in case you will need to wipe and search for a way to access twrp-saved pattern.
You could also try the google feature "find my device" and change pattern, but as phone its encrypted i dont really think it will work.
Click to expand...
Click to collapse
sadly the "find my phone" doesn't help
and in TWRP it asks for the key too and when i press cancel and try to go to data/system where the pass key is there is nothing (it must be encrypted as well)
and twrp says that my data is 0mb and can't even back it up because it's encrypted
Ok, but it doesnt say that data will be wiped, so you can try a lot of patterns.
Unfortunatelly theres no way to bypass because data is encrypted, you should try again and again and prepare yourself for a complete wipe.
cuper22 said:
i have the phone updated to android pie and rooted with magisk the latest version and i have twrp recovery on it
but while installing one of the mods (youtube vanced) and after it rebooted the phone asked for my pattern (not on the lock screen but the encrypted startup feature which i didn't turn on but i have changed my pattern a few days ago but i use the fingerprint always on the phone)
i forgot the pattern for the phone and i tried on it and it says 9 more tries and my phone will be wiped
is there a way to find the pattern on my google account since it's linked to the phone and it automatically uploads it to the cloud ? or is there a way to bypass it ?
Note:i know it sound like i stole the phone but i have proof of ownership if anyone wants(the box and the google account linked to it are mine and is linked to this account)
thanks in advance
Click to expand...
Click to collapse
What twrp did u use I keep reading it's bricks in pie
rob420p said:
What twrp did u use I keep reading it's bricks in pie
Click to expand...
Click to collapse
the one posted here on(although i'm sure i'm not using it correctly since every time i need to open it i need to fastboot boot twrb.img) it's been like that since 8.1
cuper22 said:
the one posted here on(although i'm sure i'm not using it correctly since every time i need to open it i need to fastboot boot twrb.img) it's been like that since 8.1
Click to expand...
Click to collapse
That's some bugs I've heard about it.on the post it recommends not useing that one for pie.u might want to look on Google I did see something about a emcrptiin patch