Galaxy S4 Rooting will be impossible on newer stock kernels, but this is a good thing.

[Nicktrance]

A post on XDA developers has cased some unnecessary drama due to people misunderstanding the title:  [info] Rooting will be impossible on newer stock kernels

 

 

Samsung will be implementing a new feature which prevents processes (such as malware, exploits or SU) from changing from a normal user to root by using SETUID. However a custom kernel will still allow us to achieve root access.

 

Source: http://forum.xda-developers.com/showthread.php?t=2263788

Via: http://www.androidpolice.com/2013/05/05/samsung-aims-to-block-root-exploits-and-tighten-up-security-with-latest-exynos-galaxy-s4-update-but-this-is-a-good-thing/?utm_source=feedly

 

[KaareKanin]

I'll just watch and see how it plays out... but yes, the XDA crowd can be a little overly dramatic

[Master Disaster]

OK, but you need root to install a custom kernal, unless I'm missing something?

[Octagoncow]

OK, but you need root to install a custom kernal, unless I'm missing something?

At the very least, people with root can keep it. I'm sure someone will eventually find a way around Samsung's preventative measures. I do wish that companies would cut this out though. I'm still mad at Verizon for not letting me unlock my boot loader.

[Mew]

Massive bump lol

[APrettyCoolWalrus]

ok...

[ObeseWalrus]

You should be able to flash a custom kernel with the feature disabled right?

[LAwLz]

Check the date people. This is a really old thread and as far as I know, they ended up being wrong.

Someone accidentally necro'd the thread.

[ionbasa]

OK, but you need root to install a custom kernal, unless I'm missing something?

Well, you might be able to get around that with ADB. There are ways, around it, but aren't to user friendly, and increase the chances of a brick: Eg: block level erasing of the NAND.

[ComradeHX]

S4 Active from AT&T still can't install custom ROM.