Stock A500FU PERMISSIVE kernel needed

[jimbomodder]

Right so many of us use stock rom on A500FU (2015) as its a good daily driver. Not the issue is I'm useless at compiling so is there anyone who can compile a stock kernel but... permissive as standard for us viper4android users and other reason, I'm sure there are 1000s who would appreciate it. I can provide the stock boot if nessacary

Sent from my SM-A500FU

 

[ashyx]

Right so many of us use stock rom on A500FU (2015) as its a good daily driver. Not the issue is I'm useless at compiling so is there anyone who can compile a stock kernel but... permissive as standard for us viper4android users and other reason, I'm sure there are 1000s who would appreciate it. I can provide the stock boot if nessacary

Sent from my SM-A500FU

Here you go:
A500FUXXU1BOL1_permissive_boot

.

 

[jimbomodder]

Here you go:
A500FUXXU1BOL1_permissive_boot

.

Thanks man but it hangs on splash then reboots constantly

Sent from my SM-A500FU

 

[ashyx]

Thanks man but it hangs on splash then reboots constantly

Sent from my SM-A500FU

Which firmware build are you on?
Can you post up your boot.img?

Try this one: A500FUXXU1BOL1_permissive_boot

 

[jimbomodder]

Which firmware build are you on?
Can you post up your boot.img?

Here you go

 

[jimbomodder]

Which firmware build are you on?
Can you post up your boot.img?

Try this one: A500FUXXU1BOL1_permissive_boot

Get kernel warning but just hangs at splash.

Sent from my SM-A500FU

 

[ashyx]

Get kernel warning but just hangs at splash.

Sent from my SM-A500FU

I have recompiled the kernel with no changes except set the enforcing flag to false and used your ramdisk.
If this doesn't boot then Samsungs source code is probably borked.
I have also uploaded a simply unpacked and repacked kernel with absolutely no changes. If this doesn't boot then there's an issue with simply repacking the kernel which could be because it is unsigned. This is not the first time Ive had this happen.

https://www.androidfilehost.com/?fid=24533103863137813
https://www.androidfilehost.com/?fid=24533103863137814

 

[jimbomodder]

I have recompiled the kernel with no changes except set the enforcing flag to false and used your ramdisk.
If this doesn't boot then Samsungs source code is probably borked.
I have also uploaded a simply unpacked and repacked kernel with absolutely no changes. If this doesn't boot then there's an issue with simply repacking the kernel which could be because it is unsigned. This is not the first time Ive had this happen.

https://www.androidfilehost.com/?fid=24533103863137813
https://www.androidfilehost.com/?fid=24533103863137814

First one hangs, second boots with the warning

 

[ashyx]

First one hangs, second boots with the warning

This is the exact same situation I had with the Tab A which uses the same platform and source code: Qualcomm MSM8916 Snapdragon 410.
Looks like again Samsung have fudged up the kernel source.

Are you able to set permissive via ADB or SElinux changer?

 

[jimbomodder]

This is the exact same situation I had with the Tab A which uses the same platform and source code: Qualcomm MSM8916 Snapdragon 410.
Looks like again Samsung have fudged up the kernel source.

Are you able to set permissive via ADB or SElinux changer?

Yeah selinux changer works fine. Thanks for the efforts

 

[ashyx]

Yeah selinux changer works fine. Thanks for the efforts

Well you're lucky that actually works. It usually doesn't.
Are you sure it states permissive in settings after using SElinux changer?

 

[jimbomodder]

Well you're lucky that actually works. It usually doesn't.
Are you sure it states permissive in settings after using SElinux changer?

Yes I check it, now and again Google flags as dangerous but I keep it lol

Sent from my SM-A500FU

 

[ashyx]

Yes I check it, now and again Google flags as dangerous but I keep it lol

Sent from my SM-A500FU

Any chance I can see a screen shot of that as its unusual?

 

[jimbomodder]

Any chance I can see a screen shot of that as its unusual?

The dangerous part? It normal as ive allowed google to check for harmful apps and an app they changes the selinux is dangerous to google, ill get one soon as currently on RR

Sent From either S4, S4 mini, S5 neo, A500FU, T210, T230

 

[ashyx]

The dangerous part? It normal as ive allowed google to check for harmful apps and an app they changes the selinux is dangerous to google, ill get one soon as currently on RR

Sent From either S4, S4 mini, S5 neo, A500FU, T210, T230

Just the about page where it says permissive.

 

[jimbomodder]

Just the about page where it says permissive.

I'll get it later today:good:

 

[jimbomodder]

Just the about page where it says permissive.

Better late than never

 

[ashyx]

Highly unusual, every single Samsung 5.1.1 kernel I have compiled always has the enforcing flag set in the configuration without the ability to override unless the kernel is custom.

 

[jimbomodder]

Highly unusual, every single Samsung 5.1.1 kernel I have compiled always has the enforcing flag set in the configuration without the ability to override unless the kernel is custom.

Well it's actually 5.0.2, I just changed it in build prop. I also deleted some of the security apks and no longer get a warning that it's permissive and need to reboot, also the smart manager says system is secure. Running viper4android just fine