need help with this?

[gyit918]

this happend

[gyit918]

[vinaykharayat]

You are also pasting '$', please paste commands properly

[gyit918]

hu

[gyit918]

huh??

[gyit918]

wdym by that??

[gyit918]

wait how do i get rid of this dollar s

[vinaykharayat]

setenforce Permissive This command should do the work.

[gyit918]

so what did that do??

[gyit918]

and when its permissive does that mean it has android root??

[gyit918]

its still enforcing

[gyit918]

[gyit918]

its not doing anything

[gyit918]

[gyit918]

how do i check for root

[gyit918]

dude you there

[gyit918]

this isnt working

[gyit918]

well its saying its enforcing why??

[gyit918]

i did it all right

[gyit918]

did i need to remove roofts verifaction

[vinaykharayat]

Did you run the cranberry.sh and rooted successfully?

[gyit918]

Did you run the cranberry.sh and rooted successfully?

idk

[gyit918]

it said for the last line reboot and enjoy

[gyit918]

but its still enforcing

[vinaykharayat]

Rooting does not have anything to do with SELinux enforcing or permissive. Although you will have restrictions on apps that modifies your system files like lucky patcher. To make it simple for you please tell me for what reason you need to root your chromebook?

[gyit918]

Rooting does not have anything to do with SELinux enforcing or permissive. Although you will have restrictions on apps that modifies your system files like lucky patcher. To make it simple for you please tell me for what reason you need to root your chromebook?

its something i wanted to do a long time thats all

[gyit918]

the reason i wanted to root is bc

[gyit918]

for something

[gyit918]

Rooting does not have anything to do with SELinux enforcing or permissive. Although you will have restrictions on apps that modifies your system files like lucky patcher. To make it simple for you please tell me for what reason you need to root your chromebook?

then why does it matter for se linux

[gyit918]

so how do i give apps root permission then

[supechicken]

So can you puts all in a comment and don’t split them to separate comments

[vinaykharayat]

Rooting does not have anything to do with SELinux enforcing or permissive. Although you will have restrictions on apps that modifies your system files like lucky patcher. To make it simple for you please tell me for what reason you need to root your chromebook?

its something i wanted to do a long time thats all

If you don't know why you need to root then I would suggest not to root. You are trying to do something that you don't understand and you might end up messing up your system. Please don't root until you have a solid reason to root. Have a nice day!

[gyit918]

i did fuck it up one time but fixed it

[gyit918]

and the only reason i want to root is to hack apps dont ask why

[gyit918]

so what do i do now

[gyit918]

plz help me

[gyit918]

my apps still work

[gyit918]

So can you puts all in a comment and don’t split them to separate comments

sure

[gyit918]

well anyone i have no root or do i what should it say for a success

[CerisWhite]

@gyit918 @vinaykharayat For the record, the correct command is setenforce 0, and the change doesn't apply to the selinux file. setenforce applies the change in RAM, and you can check the current status by doing getenforce

Rooting does not have anything to do with SELinux enforcing or permissive.

As of <insert version of ChromeOS where android 9 began being shipped>, it's not possible to use a rooted image without SELinux being set to permissive, so, yes, rooting has everything to do with SELinux being set to permissive.

If you have a question, please do not spam the thread with multiple small responses. Please make one large message with more info on what's going on so we can better assist you in the future.

[vinaykharayat]

@gyit918 @vinaykharayat For the record, the correct command is setenforce 0, and the change doesn't apply to the selinux file. setenforce applies the change in RAM, and you can check the current status by doing getenforce

Rooting does not have anything to do with SELinux enforcing or permissive.

As of <insert version of ChromeOS where android 9 began being shipped>, it's not possible to use a rooted image without SELinux being set to permissive, so, yes, rooting has everything to do with SELinux being set to permissive.

If you have a question, please do not spam the thread with multiple small responses. Please make one large message with more info on what's going on so we can better assist you in the future.

Actually what I meant is rooting system wont change SELinux nor it is a validation to successful root. Correct me if I am wrong.

[CerisWhite]

SELinux has to be set to permissive in order for the android system to work if cranberry.sh was successful. Otherwise, it will fail to load properly and apps will stay stuck in "loading" because the android image did not initialize properly. My script does this automatically by creating an upstart file that automatically sets SELinux to permissive on boot, so it is partially indicative of a successful run.

TL;DR: We have to remove the security for root to work on ChromeOS, period.